I keep getting 503 errors from PyPI that go away after I clear my
cookies.
The entire cycle is as follows:
1. Visit PyPI, log in (because I need to do some maintenance or
something of my packages).
2. Things continue to work for about a week.
3. Visit PyPI, get a 503 error from Varnish after
A bitbucket user informs me angrily that he cannot use the version of reportlab
that's latest on pypi because it has a dependency
pillow==2.0.0,=2.4.0
which is now treated as an 'and' condition by setuptools 8.0 so can not be
satisfied.
In our latest code we have removed the '==2.0.0,', but
On Dec 15, 2014, at 6:03 AM, Robin Becker ro...@reportlab.com wrote:
A bitbucket user informs me angrily that he cannot use the version of
reportlab that's latest on pypi because it has a dependency
pillow==2.0.0,=2.4.0
which is now treated as an 'and' condition by setuptools 8.0 so
Donald Stufft schreef op 15-12-14 13:20:
On Dec 15, 2014, at 6:03 AM, Robin Becker ro...@reportlab.com wrote:
A bitbucket user informs me angrily that he cannot use the version of reportlab
that's latest on pypi because it has a dependency
pillow==2.0.0,=2.4.0
which is now treated as an
On Dec 15, 2014, at 9:05 AM, Maurits van Rees m.van.r...@zestsoftware.nl
wrote:
Donald Stufft schreef op 15-12-14 13:20:
On Dec 15, 2014, at 6:03 AM, Robin Becker ro...@reportlab.com wrote:
A bitbucket user informs me angrily that he cannot use the version of
reportlab that's latest
On Mon, Dec 15, 2014 at 12:26 PM, Donald Stufft don...@stufft.io wrote:
On Dec 15, 2014, at 9:05 AM, Maurits van Rees m.van.r...@zestsoftware.nl
wrote:
Donald Stufft schreef op 15-12-14 13:20:
On Dec 15, 2014, at 6:03 AM, Robin Becker ro...@reportlab.com wrote:
A bitbucket user informs
On Dec 15, 2014, at 1:15 PM, Jim Fulton j...@zope.com wrote:
import pkg_resources
r = pkg_resources.Requirement.parse(five.localsitemanager2.0dev)
'2.0.5' in r
False
r = pkg_resources.Requirement.parse(five.localsitemanager2.0.dev0)
'2.0.5' in r
True
I have a feeling the definition
On Dec 15, 2014, at 1:26 PM, Donald Stufft don...@stufft.io wrote:
On Dec 15, 2014, at 1:15 PM, Jim Fulton j...@zope.com wrote:
import pkg_resources
r = pkg_resources.Requirement.parse(five.localsitemanager2.0dev)
'2.0.5' in r
False
r =
On Dec 15, 2014, at 1:27 PM, Jim Fulton j...@zope.com wrote:
I think the changes in version management in setuptools 8 are a great
step forward,
but I think the transition is going to hurt a lot.
For buildout, I'm thinking of of releasing 2.3.1 that reverts the
changes in 2.3 and
adds
+1 - I think thats a great idea. We've had to pin setuptools 8 in
the OpenStack ecosystem too.
It would have been nice to offer some period of time where the cases
which were going to change would have warned. I realise thats
non-trivial, but this is systemic infrastructure at the core of our
On Dec 15, 2014, at 1:41 PM, Robert Collins robe...@robertcollins.net wrote:
+1 - I think thats a great idea. We've had to pin setuptools 8 in
the OpenStack ecosystem too.
As far as I’m aware, Openstack is just about ready to unpin setuptools. I
believe
the only thing holding it back is a
On Mon, Dec 15, 2014 at 1:45 PM, Donald Stufft don...@stufft.io wrote:
On Dec 15, 2014, at 1:27 PM, Jim Fulton j...@zope.com wrote:
I think the changes in version management in setuptools 8 are a great
step forward,
but I think the transition is going to hurt a lot.
For buildout, I'm
We're currently pinned -
http://lists.openstack.org/pipermail/openstack-dev/2014-December/052985.html
- we tried a fix, it broke things more, so we rolled it back and are
now working on a new one - https://review.openstack.org/#/c/141667/ -
which will simply *stop including version data* in our
A new setuptools release is out that should fix the 2.0.5 in dev bug.
On Dec 15, 2014, at 1:44 PM, Donald Stufft don...@stufft.io wrote:
On Dec 15, 2014, at 1:26 PM, Donald Stufft don...@stufft.io wrote:
On Dec 15, 2014, at 1:15 PM, Jim Fulton j...@zope.com wrote:
import
Donald Stufft schreef op 15-12-14 18:26:
On Dec 15, 2014, at 9:05 AM, Maurits van Rees m.van.r...@zestsoftware.nl
wrote:
But I now run into unexpected behaviour when two packages have a constraint on the
same third package. For example one has 'zest.releaser==3.50' and another has
Great. We're gonna hopefully release pip 6 this week.
On Dec 15, 2014, at 5:27 PM, Maurits van Rees m.van.r...@zestsoftware.nl
wrote:
Donald Stufft schreef op 15-12-14 18:26:
On Dec 15, 2014, at 9:05 AM, Maurits van Rees m.van.r...@zestsoftware.nl
wrote:
But I now run into
Jim Fulton schreef op 15-12-14 19:51:
On Mon, Dec 15, 2014 at 1:45 PM, Donald Stufft don...@stufft.io wrote:
On Dec 15, 2014, at 1:27 PM, Jim Fulton j...@zope.com wrote:
I think the changes in version management in setuptools 8 are a great
step forward,
but I think the transition is going to
Maurits van Rees schreef op 15-12-14 23:50:
TMP2/setuptools-8.0.4-py2.7.egg/pkg_resources.py:2425: RuntimeWarning:
'zc.buildout-2.3.0 ()' is being parsed as a legacy, non PEP 440,
version. You may find odd behavior and sort order. In particular it will
be sorted as less than 0.0. It is recommend
On Dec 15, 2014, at 6:46 PM, Maurits van Rees m.van.r...@zestsoftware.nl
wrote:
Maurits van Rees schreef op 15-12-14 23:50:
TMP2/setuptools-8.0.4-py2.7.egg/pkg_resources.py:2425: RuntimeWarning:
'zc.buildout-2.3.0 ()' is being parsed as a legacy, non PEP 440,
version. You may find odd
Jim Fulton schreef op 15-12-14 19:15:
Buildout doesn't try to merge dependency requirements from different packages.
It just installs packages and their dependencies and builds up a working set.
It does merge constraints from the versions section (if any) with
whatever requirement
it's working
On Mon, Dec 15, 2014 at 12:00 AM, Marius Gedminas mar...@pov.lt wrote:
I keep getting 503 errors from PyPI that go away after I clear my
cookies.
The entire cycle is as follows:
1. Visit PyPI, log in (because I need to do some maintenance or
something of my packages).
2. Things
On Dec 16, 2014, at 1:42 AM, anatoly techtonik techto...@gmail.com wrote:
On Tue, Dec 16, 2014 at 2:48 AM, Donald Stufft don...@stufft.io wrote:
On Dec 15, 2014, at 6:46 PM, Maurits van Rees m.van.r...@zestsoftware.nl
wrote:
Maurits van Rees schreef op 15-12-14 23:50:
22 matches
Mail list logo
