Hello community,
here is the log from the commit of package python-docformatter for
openSUSE:Factory checked in at 2018-06-02 12:04:35
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-docformatter (Old)
and /work/SRC/openSUSE:Factory/.python-docformatter.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-docformatter"
Sat Jun 2 12:04:35 2018 rev:1 rq:612072 version:1.0
Changes:
--------
New Changes file:
--- /dev/null 2018-05-30 11:41:29.140556178 +0200
+++
/work/SRC/openSUSE:Factory/.python-docformatter.new/python-docformatter.changes
2018-06-02 12:04:36.468583305 +0200
@@ -0,0 +1,14 @@
+-------------------------------------------------------------------
+Thu May 24 17:31:41 UTC 2018 - [email protected]
+
+- Update to version 1.0
+ * Document and test disabling of wrapping
+ * Add @kapsh
+ * Make text wrapping trigger more conservative
+ * Adds support for argument lists
+- Spec file cleanups
+
+-------------------------------------------------------------------
+Tue Nov 7 18:41:21 UTC 2017 - [email protected]
+
+- initial version
New:
----
docformatter-1.0.tar.gz
python-docformatter.changes
python-docformatter.spec
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ python-docformatter.spec ++++++
#
# spec file for package python-docformatter
#
# Copyright (c) 2018 SUSE LINUX GmbH, Nuernberg, Germany.
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
# upon. The license for this file, and modifications and additions to the
# file, is the same license as for the pristine package itself (unless the
# license for the pristine package is not an Open Source License, in which
# case the license is the MIT License). An "Open Source License" is a
# license that conforms to the Open Source Definition (Version 1.9)
# published by the Open Source Initiative.
# Please submit bugfixes or comments via http://bugs.opensuse.org/
%{?!python_module:%define python_module() python-%{**} python3-%{**}}
Name: python-docformatter
Version: 1.0
Release: 0
License: MIT
Summary: Formats docstrings to follow PEP 257
Url: https://github.com/myint/docformatter
Group: Development/Languages/Python
Source:
https://files.pythonhosted.org/packages/source/d/docformatter/docformatter-%{version}.tar.gz
BuildRequires: %{python_module devel}
BuildRequires: %{python_module setuptools}
BuildRequires: fdupes
BuildRequires: python-rpm-macros
# SECTION test requirements
BuildRequires: %{python_module untokenize}
# /SECTION
Requires: python-untokenize
BuildArch: noarch
%python_subpackages
%description
Docformatter currently automatically formats docstrings to follow a
subset of the PEP 257 conventions. Below are the relevant items quoted
from PEP 257.
- For consistency, always use triple double quotes around docstrings.
- Triple quotes are used even though the string fits on one line.
- Multi-line docstrings consist of a summary line just like a one-line
docstring, followed by a blank line, followed by a more elaborate
description.
- The BDFL recommends inserting a blank line between the last paragraph
in a multi-line docstring and its closing quotes, placing the closing
quotes on a line by themselves.
docformatter also handles some of the PEP 8 conventions.
- Don't write string literals that rely on significant trailing
whitespace. Such trailing whitespace is visually indistinguishable
and some editors (or more recently, reindent.py) will trim them.
%prep
%setup -q -n docformatter-%{version}
sed -i -e '/^#!\//, 1d' docformatter.py
%build
%python_build
%install
%python_install
%python_expand %fdupes %{buildroot}%{$python_sitelib}
%check
%python_exec setup.py test
%files %{python_files}
%doc AUTHORS.rst README.rst
%python3_only %{_bindir}/docformatter
%{python_sitelib}/*
%changelog
