Hello community,
here is the log from the commit of package python-nine for openSUSE:Factory
checked in at 2020-03-31 17:14:00
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-nine (Old)
and /work/SRC/openSUSE:Factory/.python-nine.new.3160 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-nine"
Tue Mar 31 17:14:00 2020 rev:3 rq:789771 version:1.1.0
Changes:
--------
--- /work/SRC/openSUSE:Factory/python-nine/python-nine.changes 2018-12-24
11:40:09.281517983 +0100
+++ /work/SRC/openSUSE:Factory/.python-nine.new.3160/python-nine.changes
2020-03-31 17:14:10.155586599 +0200
@@ -1,0 +2,6 @@
+Mon Mar 30 11:26:40 UTC 2020 - pgaj...@suse.com
+
+- version update to 1.1.0
+ * no upstream changelog found
+
+-------------------------------------------------------------------
Old:
----
nine-1.0.0.tar.gz
New:
----
nine-1.1.0.tar.gz
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ python-nine.spec ++++++
--- /var/tmp/diff_new_pack.Y78cUS/_old 2020-03-31 17:14:14.111589111 +0200
+++ /var/tmp/diff_new_pack.Y78cUS/_new 2020-03-31 17:14:14.115589114 +0200
@@ -1,7 +1,7 @@
#
# spec file for package python-nine
#
-# Copyright (c) 2018 SUSE LINUX GmbH, Nuernberg, Germany.
+# Copyright (c) 2020 SUSE LLC
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
@@ -17,15 +17,15 @@
%{?!python_module:%define python_module() python-%{**} python3-%{**}}
-%bcond_without test
Name: python-nine
-Version: 1.0.0
+Version: 1.1.0
Release: 0
Summary: Python 2 / 3 compatibility, like six, but favouring Python 3
License: SUSE-Public-Domain
Group: Development/Languages/Python
URL: https://github.com/nandoflorestan/nine
Source:
https://files.pythonhosted.org/packages/source/n/nine/nine-%{version}.tar.gz
+BuildRequires: %{python_module pytest}
BuildRequires: %{python_module setuptools}
BuildRequires: python-rpm-macros
BuildArch: noarch
@@ -46,10 +46,8 @@
%install
%python_install
-%if %{with test}
%check
-%python_exec setup.py test
-%endif
+%pytest
%files %{python_files}
%license LICENSE.rst
++++++ nine-1.0.0.tar.gz -> nine-1.1.0.tar.gz ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/nine-1.0.0/PKG-INFO new/nine-1.1.0/PKG-INFO
--- old/nine-1.0.0/PKG-INFO 2016-05-22 20:28:16.000000000 +0200
+++ new/nine-1.1.0/PKG-INFO 2020-01-21 21:10:22.000000000 +0100
@@ -1,6 +1,6 @@
Metadata-Version: 1.1
Name: nine
-Version: 1.0.0
+Version: 1.1.0
Summary: Python 2 / 3 compatibility, like six, but favouring Python 3
Home-page: https://github.com/nandoflorestan/nine
Author: Nando Florestan
@@ -12,11 +12,8 @@
When the best Python 2/Python 3 compatibility modules -- especially
the famous
`*six* library invented by Benjamin Peterson
<https://pypi.python.org/pypi/six>`_
-- were created, they were written from the point of view of a Python 2
- programmer starting to grok Python 3.
-
- But it is 2016. Python 3.5 is here. 3.5!!!
-
- If you use *six*, your code is compatible, but stuck in Python 2
idioms.
+ programmer starting to grok Python 3. If you use *six*,
+ your code is compatible, but stuck in Python 2 idioms.
**nine** turns **six** upside down. You write your code using Python 3
idioms
-- as much as possible --, and it is the Python 2 "version" that is
patched.
@@ -25,22 +22,24 @@
When thou writeth Python, thou shalt write Python 3 and,
just for a little longer, ensure that the thing worketh on Python 2.7.
- Honestly you should not spend one thought on Python 2.6 anymore, it is
- `no longer supported
<https://mail.python.org/pipermail/python-dev/2013-September/128287.html>`_
- since its final release (2.6.9) in October 2013. Nobody uses 3.0 or
3.1 either.
-
- Python 2.7 will finally meet its demise in the year 2020. So, starting
now,
- thine codebase shall look more like 3 than 2.
-
*nine* facilitates this point of view. You can write code
that is as 3ish as possible while still supporting 2.6.
- Very comfortable for new projects.
For instance, you don't type ``unicode`` anymore, you type ``str``,
and *nine*
makes ``str`` point to ``unicode`` on Python 2 (if you use our
boilerplate).
Also, ``map``, ``zip`` and ``filter`` have Python 3 behaviour, on
Python 2,
meaning they return iterators, not lists.
+ Honestly you should not spend one thought on Python 2.6 anymore, it is
+ `no longer supported
<https://mail.python.org/pipermail/python-dev/2013-September/128287.html>`_
+ since its final release (2.6.9) in October 2013. Nobody uses 3.0 or
3.1 either.
+
+ Python 2.7 has finally met its demise on the first day of 2020.
+
+ *nine* is extremely stable and unlikely to change since it solves an
old
+ problem that never changes. Nobody should be surprised if *nine* isn't
+ updated for months or even years.
+
The author(s) of *nine* donate this module to the public domain.
To understand most of the intricacies involved in achieving 2&3
compatibility
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/nine-1.0.0/README.rst new/nine-1.1.0/README.rst
--- old/nine-1.0.0/README.rst 2016-05-22 19:57:43.000000000 +0200
+++ new/nine-1.1.0/README.rst 2020-01-21 20:36:36.000000000 +0100
@@ -4,11 +4,8 @@
When the best Python 2/Python 3 compatibility modules -- especially the famous
`*six* library invented by Benjamin Peterson
<https://pypi.python.org/pypi/six>`_
-- were created, they were written from the point of view of a Python 2
-programmer starting to grok Python 3.
-
-But it is 2016. Python 3.5 is here. 3.5!!!
-
-If you use *six*, your code is compatible, but stuck in Python 2 idioms.
+programmer starting to grok Python 3. If you use *six*,
+your code is compatible, but stuck in Python 2 idioms.
**nine** turns **six** upside down. You write your code using Python 3 idioms
-- as much as possible --, and it is the Python 2 "version" that is patched.
@@ -17,22 +14,24 @@
When thou writeth Python, thou shalt write Python 3 and,
just for a little longer, ensure that the thing worketh on Python 2.7.
-Honestly you should not spend one thought on Python 2.6 anymore, it is
-`no longer supported
<https://mail.python.org/pipermail/python-dev/2013-September/128287.html>`_
-since its final release (2.6.9) in October 2013. Nobody uses 3.0 or 3.1 either.
-
-Python 2.7 will finally meet its demise in the year 2020. So, starting now,
-thine codebase shall look more like 3 than 2.
-
*nine* facilitates this point of view. You can write code
that is as 3ish as possible while still supporting 2.6.
-Very comfortable for new projects.
For instance, you don't type ``unicode`` anymore, you type ``str``, and *nine*
makes ``str`` point to ``unicode`` on Python 2 (if you use our boilerplate).
Also, ``map``, ``zip`` and ``filter`` have Python 3 behaviour, on Python 2,
meaning they return iterators, not lists.
+Honestly you should not spend one thought on Python 2.6 anymore, it is
+`no longer supported
<https://mail.python.org/pipermail/python-dev/2013-September/128287.html>`_
+since its final release (2.6.9) in October 2013. Nobody uses 3.0 or 3.1 either.
+
+Python 2.7 has finally met its demise on the first day of 2020.
+
+*nine* is extremely stable and unlikely to change since it solves an old
+problem that never changes. Nobody should be surprised if *nine* isn't
+updated for months or even years.
+
The author(s) of *nine* donate this module to the public domain.
To understand most of the intricacies involved in achieving 2&3 compatibility
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/nine-1.0.0/nine/__init__.py
new/nine-1.1.0/nine/__init__.py
--- old/nine-1.0.0/nine/__init__.py 2016-05-22 20:06:32.000000000 +0200
+++ new/nine-1.1.0/nine/__init__.py 2020-01-21 20:13:08.000000000 +0100
@@ -6,10 +6,10 @@
"""
import sys
+
# Test for Python 2, not 3; don't get bitten when Python 4 appears:
IS_PYTHON2 = (sys.version_info[0] == 2)
IS_PYPY = hasattr(sys, 'pypy_translation_info')
-del sys
from importlib import import_module
if IS_PYTHON2: # Rename Python 2 builtins so they become like Python 3
@@ -127,7 +127,6 @@
'reprlib': 'repr',
'socketserver': 'SocketServer',
'_thread': 'thread',
- '_dummy_thread': 'dummy_thread',
'tkinter': 'Tkinter',
'http.client': 'httplib',
'http.cookiejar': 'cookielib',
@@ -184,6 +183,10 @@
'urllib.request:CacheFTPHandler': 'urllib2:CacheFTPHandler',
'urllib.request:UnknownHandler': 'urllib2:UnknownHandler',
}
+if sys.version_info < (3, 9):
+ # dummy_thread has been removed from Python 3.9
+ # https://bugs.python.org/issue37312
+ _moved['_dummy_thread'] = 'dummy_thread'
def nimport(spec):
@@ -214,3 +217,6 @@
name = None
module = import_module(module)
return getattr(module, name) if name else module
+
+# don't export nine.six
+del sys
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/nine-1.0.0/nine.egg-info/PKG-INFO
new/nine-1.1.0/nine.egg-info/PKG-INFO
--- old/nine-1.0.0/nine.egg-info/PKG-INFO 2016-05-22 20:28:16.000000000
+0200
+++ new/nine-1.1.0/nine.egg-info/PKG-INFO 2020-01-21 21:10:22.000000000
+0100
@@ -1,6 +1,6 @@
Metadata-Version: 1.1
Name: nine
-Version: 1.0.0
+Version: 1.1.0
Summary: Python 2 / 3 compatibility, like six, but favouring Python 3
Home-page: https://github.com/nandoflorestan/nine
Author: Nando Florestan
@@ -12,11 +12,8 @@
When the best Python 2/Python 3 compatibility modules -- especially
the famous
`*six* library invented by Benjamin Peterson
<https://pypi.python.org/pypi/six>`_
-- were created, they were written from the point of view of a Python 2
- programmer starting to grok Python 3.
-
- But it is 2016. Python 3.5 is here. 3.5!!!
-
- If you use *six*, your code is compatible, but stuck in Python 2
idioms.
+ programmer starting to grok Python 3. If you use *six*,
+ your code is compatible, but stuck in Python 2 idioms.
**nine** turns **six** upside down. You write your code using Python 3
idioms
-- as much as possible --, and it is the Python 2 "version" that is
patched.
@@ -25,22 +22,24 @@
When thou writeth Python, thou shalt write Python 3 and,
just for a little longer, ensure that the thing worketh on Python 2.7.
- Honestly you should not spend one thought on Python 2.6 anymore, it is
- `no longer supported
<https://mail.python.org/pipermail/python-dev/2013-September/128287.html>`_
- since its final release (2.6.9) in October 2013. Nobody uses 3.0 or
3.1 either.
-
- Python 2.7 will finally meet its demise in the year 2020. So, starting
now,
- thine codebase shall look more like 3 than 2.
-
*nine* facilitates this point of view. You can write code
that is as 3ish as possible while still supporting 2.6.
- Very comfortable for new projects.
For instance, you don't type ``unicode`` anymore, you type ``str``,
and *nine*
makes ``str`` point to ``unicode`` on Python 2 (if you use our
boilerplate).
Also, ``map``, ``zip`` and ``filter`` have Python 3 behaviour, on
Python 2,
meaning they return iterators, not lists.
+ Honestly you should not spend one thought on Python 2.6 anymore, it is
+ `no longer supported
<https://mail.python.org/pipermail/python-dev/2013-September/128287.html>`_
+ since its final release (2.6.9) in October 2013. Nobody uses 3.0 or
3.1 either.
+
+ Python 2.7 has finally met its demise on the first day of 2020.
+
+ *nine* is extremely stable and unlikely to change since it solves an
old
+ problem that never changes. Nobody should be surprised if *nine* isn't
+ updated for months or even years.
+
The author(s) of *nine* donate this module to the public domain.
To understand most of the intricacies involved in achieving 2&3
compatibility
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/nine-1.0.0/setup.cfg new/nine-1.1.0/setup.cfg
--- old/nine-1.0.0/setup.cfg 2016-05-22 20:28:16.000000000 +0200
+++ new/nine-1.1.0/setup.cfg 2020-01-21 21:10:22.000000000 +0100
@@ -4,5 +4,4 @@
[egg_info]
tag_build =
tag_date = 0
-tag_svn_revision = 0
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/nine-1.0.0/setup.py new/nine-1.1.0/setup.py
--- old/nine-1.0.0/setup.py 2016-05-22 20:28:04.000000000 +0200
+++ new/nine-1.1.0/setup.py 2020-01-21 21:10:22.000000000 +0100
@@ -17,7 +17,7 @@
setup(
name="nine",
- version='1.0.0',
+ version='1.1.0',
description="Python 2 / 3 compatibility, like six, but favouring Python 3",
long_description=long_description,
url='https://github.com/nandoflorestan/nine',
