Hello community, here is the log from the commit of package python-yapf for openSUSE:Factory checked in at 2018-03-05 13:37:59 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/python-yapf (Old) and /work/SRC/openSUSE:Factory/.python-yapf.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Package is "python-yapf" Mon Mar 5 13:37:59 2018 rev:1 rq:580907 version:0.19.0 Changes: -------- New Changes file: --- /dev/null 2018-03-01 08:56:54.644963210 +0100 +++ /work/SRC/openSUSE:Factory/.python-yapf.new/python-yapf.changes 2018-03-05 13:38:06.119412753 +0100 @@ -0,0 +1,4 @@ +------------------------------------------------------------------- +Fri Oct 20 16:19:54 UTC 2017 - toddrme2178@gmail.com + +- initial version New: ---- python-yapf.changes python-yapf.spec yapf-0.19.0.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ python-yapf.spec ++++++ # # spec file for package python-yapf # # Copyright (c) 2017 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-%{**}} %bcond_without test 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 Group: Development/Languages/Python Source: https://files.pythonhosted.org/packages/source/y/yapf/yapf-%{version}.tar.gz BuildRequires: %{python_module devel} BuildRequires: %{python_module setuptools} BuildRequires: fdupes BuildRequires: python-rpm-macros %if %{with test} BuildRequires: %{python_module nose} BuildRequires: python-futures %endif BuildArch: noarch %ifpython2 Recommends: python-futures %endif Requires(post): update-alternatives Requires(postun): update-alternatives %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. %prep %setup -q -n yapf-%{version} %build %python_build %install %python_install %python_expand %fdupes %{buildroot}%{$python_sitelib} %python_clone -a %{buildroot}%{_bindir}/yapf %if %{with test} %check %python_expand nosetests-%{$python_bin_suffix} %endif %post %python_install_alternative yapf %postun %python_uninstall_alternative yapf %files %{python_files} %defattr(-,root,root,-) %doc README.rst %python_alternative %{_bindir}/yapf %{python_sitelib}/* %changelog