Hello community, here is the log from the commit of package python-yapf for openSUSE:Factory checked in at 2018-05-04 11:30:14 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/python-yapf (Old) and /work/SRC/openSUSE:Factory/.python-yapf.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-yapf" Fri May 4 11:30:14 2018 rev:2 rq:603215 version:0.19.0 Changes: -------- --- /work/SRC/openSUSE:Factory/python-yapf/python-yapf.changes 2018-03-05 13:38:06.119412753 +0100 +++ /work/SRC/openSUSE:Factory/.python-yapf.new/python-yapf.changes 2018-05-04 11:30:15.330102502 +0200 @@ -1,0 +2,5 @@ +Sun Mar 4 11:06:23 UTC 2018 - [email protected] + +- Trim description and focus on the package, not the process. + +------------------------------------------------------------------- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ python-yapf.spec ++++++ --- /var/tmp/diff_new_pack.xfBAUr/_old 2018-05-04 11:30:15.854083277 +0200 +++ /var/tmp/diff_new_pack.xfBAUr/_new 2018-05-04 11:30:15.858083129 +0200 @@ -1,7 +1,7 @@ # # spec file for package python-yapf # -# Copyright (c) 2017 SUSE LINUX GmbH, Nuernberg, Germany. +# 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 @@ -13,6 +13,7 @@ # published by the Open Source Initiative. # Please submit bugfixes or comments via http://bugs.opensuse.org/ +# %{?!python_module:%define python_module() python-%{**} python3-%{**}} @@ -20,10 +21,10 @@ Name: python-yapf Version: 0.19.0 Release: 0 -License: Apache-2.0 Summary: A formatter for Python code -Url: https://github.com/google/yapf +License: Apache-2.0 Group: Development/Languages/Python +Url: https://github.com/google/yapf Source: https://files.pythonhosted.org/packages/source/y/yapf/yapf-%{version}.tar.gz BuildRequires: %{python_module devel} BuildRequires: %{python_module setuptools} @@ -43,23 +44,14 @@ %python_subpackages %description -Most of the current formatters for Python --- e.g., autopep8, and pep8ify --- -are made to remove lint errors from code. This has some obvious limitations. -For instance, code that conforms to the PEP 8 guidelines may not be -reformatted. But it doesn't mean that the code looks good. - -YAPF takes a different approach. It's based off of 'clang-format', developed by -Daniel Jasper. In essence, the algorithm takes the code and reformats it to the -best formatting that conforms to the style guide, even if the original code -didn't violate the style guide. The idea is also similar to the 'gofmt' tool for -the Go programming language: end all holy wars about formatting - if the whole -codebase of a project is simply piped through YAPF whenever modifications are -made, the style remains consistent throughout the project and there's no point -arguing about style in every code review. - -The ultimate goal is that the code YAPF produces is as good as the code that a -programmer would write if they were following the style guide. It takes away -some of the drudgery of maintaining your code. +YAPF is based off clang-format and reformats it to the closest +formatting that conforms to the style guide, even if the original +code did not violate the style guide. + +This is in contrast to other formatters like autopep8 and pep8ify +which are made to only remove lint errors from code, which has some +limitations, like, code that conforms to the PEP 8 guidelines may not +be reformatted. %prep %setup -q -n yapf-%{version}
