From: zdykstra <zdykstra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: python-setuptools: update to 46.0.0.
Date: Tue, 10 Mar 2020 02:37:32 +0100 [thread overview]
Message-ID: <20200310013732.Vl5CudrRG-_WitFbJ_EVRqIQqRlKXaR0_-RI0dAYomI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19997@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1485 bytes --]
New comment by zdykstra on void-packages repository
https://github.com/void-linux/void-packages/pull/19997#issuecomment-596857719
Comment:
> v45.0.0 dropped python2 support. Do we need to split out a v44.0.0 version for our python2 packages?
Good catch - I wish their [release history](https://pypi.org/project/setuptools/45.3.0/#history) gave any indication that they were dropping support for 2.7 after v45. It does appear to run, but throws a dramatic warning:
```
pip2 -V
/usr/lib/python2.7/site-packages/pkg_resources/py2_warn.py:22: UserWarning: Setuptools will stop working on Python 2
************************************************************
You are running Setuptools on Python 2, which is no longer
supported and
>>> SETUPTOOLS WILL STOP WORKING <<<
in a subsequent release (no sooner than 2020-04-20).
Please ensure you are installing
Setuptools using pip 9.x or later or pin to `setuptools<45`
in your environment.
If you have done those things and are still encountering
this message, please comment in
https://github.com/pypa/setuptools/issues/1458
about the steps that led to this unsupported combination.
************************************************************
sys.version_info < (3,) and warnings.warn(pre + "*" * 60 + msg + "*" * 60)
pip 19.3.1 from /usr/lib/python2.7/site-packages/pip (python 2.7)
```
I'll split this package apart into python-setuptools (v44.0.0) and python3-setuptools (v46.0.0). Stand by for the changes!
next prev parent reply other threads:[~2020-03-10 1:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19997@inbox.vuxu.org>
2020-03-10 0:11 ` zdykstra
2020-03-10 1:26 ` daniel-eys
2020-03-10 1:37 ` zdykstra [this message]
2020-03-10 1:37 ` zdykstra
2020-03-10 3:00 ` zdykstra
2020-03-10 4:12 ` python/python3-setuptools: split template, bump versions zdykstra
2020-03-10 4:34 ` zdykstra
2020-03-13 22:53 ` Piraty
2020-03-14 18:21 ` zdykstra
2020-03-14 18:48 ` Chocimier
2020-03-14 20:35 ` zdykstra
2020-03-18 23:20 ` Chocimier
2020-03-19 22:47 ` Chocimier
2020-03-19 22:47 ` [PR PATCH] [Merged]: " Chocimier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200310013732.Vl5CudrRG-_WitFbJ_EVRqIQqRlKXaR0_-RI0dAYomI@z \
--to=zdykstra@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).