Script 'mail_helper' called by obssrc
Hello community,
here is the log from the commit of package python-setuptools-version-command
for openSUSE:Factory checked in at 2022-10-08 01:26:00
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-setuptools-version-command (Old)
and
/work/SRC/openSUSE:Factory/.python-setuptools-version-command.new.2275 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-setuptools-version-command"
Sat Oct 8 01:26:00 2022 rev:2 rq:1008861 version:99.9
Changes:
--------
---
/work/SRC/openSUSE:Factory/python-setuptools-version-command/python-setuptools-version-command.changes
2020-10-13 15:43:41.653399167 +0200
+++
/work/SRC/openSUSE:Factory/.python-setuptools-version-command.new.2275/python-setuptools-version-command.changes
2022-10-08 01:26:27.986400494 +0200
@@ -1,0 +2,8 @@
+Fri Oct 7 15:29:06 UTC 2022 - Yogalakshmi Arunachalam <yarunacha...@suse.com>
+
+- Update to version 99.9
+ * Add deprecation warning to code
+ * Add deprecation notice to README
+ * Final bump of version
+
+-------------------------------------------------------------------
Old:
----
setuptools-version-command-2.2.tar.gz
New:
----
setuptools-version-command-99.9.tar.gz
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ python-setuptools-version-command.spec ++++++
--- /var/tmp/diff_new_pack.7qAFgp/_old 2022-10-08 01:26:28.334401292 +0200
+++ /var/tmp/diff_new_pack.7qAFgp/_new 2022-10-08 01:26:28.338401301 +0200
@@ -1,7 +1,7 @@
#
# spec file for package python-setuptools-version-command
#
-# Copyright (c) 2020 SUSE LLC
+# Copyright (c) 2022 SUSE LLC
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
@@ -18,7 +18,7 @@
%{?!python_module:%define python_module() python-%{**} python3-%{**}}
Name: python-setuptools-version-command
-Version: 2.2
+Version: 99.9
Release: 0
Summary: Adds a command to dynamically get the version from the VCS of
choice
License: MIT
++++++ setuptools-version-command-2.2.tar.gz ->
setuptools-version-command-99.9.tar.gz ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/setuptools-version-command-2.2/README.rst
new/setuptools-version-command-99.9/README.rst
--- old/setuptools-version-command-2.2/README.rst 2015-09-07
19:38:31.000000000 +0200
+++ new/setuptools-version-command-99.9/README.rst 2021-11-23
10:02:20.000000000 +0100
@@ -1,8 +1,22 @@
-setuptools-version-command
+setuptools-version-command
==========================
*Get version from version control instead of hardcoding it into setup.py*
+??? DEPRECATION NOTICE ???
+----------------------
+
+This package is no longer maintained. It will not evolve along with the Python
+packaging ecosystem. Specifically, as of November 2021, it will not work with
+static metadata defined in `setup.cfg` as opposed to metadata defined in
+`setup.py`.
+
+There is a good alternative: use `setuptools-scm`_ instead. This is easy to
+set up in a `setup.cfg`, see the PyPA `Packaging Python projects`_ tutorial.
+
+.. _setuptools-scm: https://pypi.org/project/setuptools-scm/
+.. _Packaging Python projects:
https://packaging.python.org/tutorials/packaging-projects/
+
introduction
------------
@@ -40,7 +54,12 @@
``version_command`` keyword argument. It can either be a str or a tuple. If
it's a str, it's interpreted as just the command to execute, for example ``git
describe``. If it's a tuple, it must have two or three elements, and have the
-form ``(command, pep440_mode[, post_mode])``.
+form ``(command, pep440_mode[, post_mode])``. ``pep440_mode`` can only be
+specified in the tuple of ``version_argument``, not as separate
+argument of ``setup``.
+
+A list of possible values for tuples passed to the ``version_command`` keyword
+argument:
:``command``: Must be ``"git describe"``, but could also support other VCS in
the future.
@@ -77,7 +96,7 @@
dev tag, that's the one that will be used for the revision number. If the
last Git tag is an open post-release tag, then that will be used. If the
last Git tag is an open pre-release tag, that will be used. In other cases,
- a post-release tag will be added.
+ a post-release tag will be added.
:``pep440_mode`` = ``"pep440-git-full``: Similar to ``"pep440-git"`` but
includes the commit hash and dirty marker (if present) in the local version
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/setuptools-version-command-2.2/setuptools_version_command.py
new/setuptools-version-command-99.9/setuptools_version_command.py
--- old/setuptools-version-command-2.2/setuptools_version_command.py
2015-09-07 19:38:31.000000000 +0200
+++ new/setuptools-version-command-99.9/setuptools_version_command.py
2021-11-23 10:02:20.000000000 +0100
@@ -5,6 +5,11 @@
import re
import subprocess
+import warnings
+
+warnings.warn('The setuptools-version-command package is deprecated, use
setuptools-scm instead. '
+ + 'See https://github.com/j0057/setuptools-version-command for
more information.')
+
# see pep440-version-regex.png
_PEP440_VERSION =
re.compile(r'^(?P<v>v)?(?:(?P<e>\d+)(?P<e_s>!))?(?P<r>\d+(?:\.\d+)*)(?:(?P<pre_ps>[\._-])?(?P<pre_t>a|alpha|b|beta|rc|c|pre|preview)(?P<pre_is>[\._-](?=\d))?(?P<pre_n>\d*))?(?:(?:(?P<post_ps>[\._-])?(?P<post_t>post|rev|r)(?P<post_is>[\._-](?=\d))?|(?P<post_im>-))(?P<post_n>(?(post_t)\d*|\d+)))?(?:(?P<dev_ps>[\._-])?(?P<dev_t>dev)(?P<dev_is>[\._-](?=\d))?(?P<dev_n>\d*))?(?:-(?P<git_rev>\d+)-(?P<git_commit>g?[0-9a-f]{4,20}))?(?P<git_dirty>-dirty)?$',
re.IGNORECASE|re.VERBOSE)
_PEP440_POST_MODE =
re.compile(r'^(?:(?P<post_ps>[\._-]?)(?P<post_t>post|rev|r)(?P<post_is>[\._-]?)|(?P<post_im>-))?$')
