Opened 6 years ago

Closed 5 years ago

Last modified 5 years ago

#8624 closed enhancement (overcomebyevents)

setuptools-34.2.0 (Python Module - Hold for too many releases)

Reported by: Douglas R. Reno Owned by: Douglas R. Reno
Priority: low Milestone: 8.1
Component: BOOK Version: SVN
Severity: normal Keywords:


New point version

Change History (12)

comment:1 by bdubbs@…, 6 years ago

Summary: setuptools (Python Module - Hold for too many releases)setuptools-30.3.0 (Python Module - Hold for too many releases)

comment:2 by Douglas R. Reno, 5 years ago

Owner: changed from blfs-book@… to Douglas R. Reno
Status: newassigned

comment:3 by Douglas R. Reno, 5 years ago

Summary: setuptools-30.3.0 (Python Module - Hold for too many releases)setuptools-34.2.0 (Python Module - Hold for too many releases)

comment:4 by Douglas R. Reno, 5 years ago

We've got a minor problem...

Upstream is only releasing this package in *.zip format until further notice as their repository disallows uploading two different file formats of the same file.

    #893: Only release sdist in zip format as warehouse now disallows releasing two different formats.

Should we still update this, or forget about it until they sort everything out?

comment:5 by ken@…, 5 years ago

I think 'warehouse' means pypi : if so, I doubt non-zip releases will happen anytime soon : I'd like to be proved wrong, but Python is "multi-platform" in a way that tar isn't.

For me (sysv) this is just a build tool for use with a few specific packages (Sphinx for llvm docs and potentially for new-style rst kernel docs, and for one module which is not in the book). Those are things I already build well after unzip, so I suggest updating this.

comment:6 by Douglas R. Reno, 5 years ago

Alright, I'll toss it in with my next commit. Still running jhalfs for 8.0-rc1 stats.

comment:7 by Douglas R. Reno, 5 years ago

Milestone: hold8.1
Traceback (most recent call last):
  File "", line 11, in <module>
    import setuptools
  File "/sources/setuptools-34.2.0/setuptools-34.2.0/setuptools/", line 12, in <module>
    import setuptools.version
  File "/sources/setuptools-34.2.0/setuptools-34.2.0/setuptools/", line 1, in <module>
    import pkg_resources
  File "/sources/setuptools-34.2.0/setuptools-34.2.0/pkg_resources/", line 70, in <module>
    import packaging.version
ImportError: No module named packaging.version
0.5 Elasped Time - setuptools-34.2.0

Either that release is broken, or it needs Python-3.6.x which I don't have installed. Moving to 8.1.

comment:8 by ken@…, 5 years ago

That might be - Python is like perl: individual developers have their own ideas about how it is easiest to proceed, and the dependencies multiply.

The difference between Python and perl is that perl usually tells you (warnings in the first step, or failures in the build) which package it now needs (search at, whereas Python can be somewhat obscure (names often either get a lot of matches, or none). And then there may be subsequent deps : no objection to moving this to 8.1, the version of setuptools which we have was working a week ago.

comment:9 by bdubbs@…, 5 years ago

Ken, Douglas and I were working this together. The problem was that when we went to install packaging, it wanted setuptools, so there is a circular dependency chain. I think we can install pip in the main python packages and use it like perl's cpan.

comment:10 by Douglas R. Reno, 5 years ago

Resolution: overcomebyevents
Status: assignedclosed

Archived setuptools and modified the python instructions to allow for Setuptools to be installed with the standard python installation.

comment:11 by bdubbs@…, 5 years ago

Milestone: 8.1m8.1

Milestone renamed

comment:12 by bdubbs@…, 5 years ago

Milestone: m8.18.1

Milestone renamed

Note: See TracTickets for help on using tickets.