[Distutils] latest setuptools appears to require six in a breaking way

[Eric Brunson]

It wasn't until recently the I realized how quickly releases to setuptools
and pip are being made, starting back in mid Dec when much of our
dependency resolution started failing.  There were three releases in the
past two days.  Four major and 22 minor releases in the past two months.
While I applaud the speed of development and the improvement in these
tools, don't you feel that breaking changes should be advertised better
before release or perhaps we should slow down the cadence for release?

I think an expectation that every setuptools user in the community start
their day by checking to see if there was a release in the past 24 hours is
a little unreasonable.  I've spent a dozen hours since 32.0.0 resolving
breakage in my own projects and assisting other developers in my org with
their setuptools issues, all the while pushing setuptools as the best
practice to do development and distribution.  Is this period of breaking
changes a short term thing that we just have to tough out for a few more
weeks?

Thanks,
e.

On Wed, Jan 25, 2017 at 9:45 AM Matthias Bussonnier <
bussonniermatthias at gmail.com> wrote:

> AFAICT this is not really an issue as this is on the release notes:
>
> https://setuptools.readthedocs.io/en/latest/history.html#v34-0-0
>
> You need to upgrade pip  (cf 3rd paragraph):
>
> > #581: Instead of vendoring the growing list of dependencies that
> Setuptools requires to function, Setuptools now requires these dependencies
> just like any other project. Unlike other projects, however, Setuptools
> cannot rely on setup_requires to demand the dependencies it needs to
> install because its own machinery would be necessary to pull those
> dependencies if not present (a bootstrapping problem). As a result,
> Setuptools no longer supports self upgrade or installation in the general
> case. Instead, users are directed to use pip to install and upgrade using
> the wheel distributions of setuptools.
>
> > Users are welcome to contrive other means to install or upgrade
> Setuptools using other means, such as pre-installing the Setuptools
> dependencies with pip or a bespoke bootstrap tool, but such usage is not
> recommended and is not supported.
>
>  >As discovered in #940, not all versions of pip will successfully
> install Setuptools from its pre-built wheel. If you encounter issues
> with “No module named six” or “No module named packaging”, especially
> following a line “Running setup.py egg_info for package setuptools”,
> then your pip is not new enough.
>
> > There’s an additional issue in pip where setuptools is upgraded
> concurrently with other source packages, described in pip #4253. The
> proposed workaround is to always upgrade Setuptools first prior to
> upgrading other packages that would upgrade Setuptools.
>
> --
> M
>
> On Wed, Jan 25, 2017 at 6:46 AM, Robin Becker <robin at reportlab.com> wrote:
> >
> > On 25/01/2017 10:41, Chris Withers wrote:
> >>
> >> Hi All,
> >>
> >> Anyone else seen this?
> >>
> >> |File
> >>
> >>
> "/home/travis/virtualenv/python2.6.9/lib/python2.6/site-packages/setuptools/__init__.py",
> >> line 10, in <module> from six.moves import filter, map ImportError: No
> >> module
> >> named six.moves|
> >>
> > My colleague just came across this when creating a new venv.
> >
> > We then installed six, but our setup then went on to complain about
> > packaging and then finally appdirs before it went through.
> >
> > Each time the fix was to manually install the thing that pip complained
> > about.
> >
> >
> >>
> >> Started happening in my nightly builds on travis after the 34.0.2
> release
> >> of
> >> setuptools. I've filed an issue here since I suspect it isn't just me:
> >>
> >> https://github.com/pypa/setuptools/issues/945
> >>
> >> cheers,
> >>
> >> Chris
> >>
> >>
> >>
> >> _______________________________________________
> >> Distutils-SIG maillist  -  Distutils-SIG at python.org
> >> https://mail.python.org/mailman/listinfo/distutils-sig
> >>
> >
> >
> > --
> > Robin Becker
> > _______________________________________________
> > Distutils-SIG maillist  -  Distutils-SIG at python.org
> > https://mail.python.org/mailman/listinfo/distutils-sig
> _______________________________________________
> Distutils-SIG maillist  -  Distutils-SIG at python.org
> https://mail.python.org/mailman/listinfo/distutils-sig
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/distutils-sig/attachments/20170125/46b5f2d8/attachment.html>