Donald Stufft schreef op 17-12-14 04:59:
On Dec 16, 2014, at 10:25 PM, Ethan Furman et...@stoneleaf.us wrote:
To continue with Maurits' use-case, in order to get /exactly/ 1.3, '===' is the
operator to use? Or are we still
discussing that? Personally, I think
pip install yourthing is 1.3
On 17 December 2014 at 02:48, Donald Stufft don...@stufft.io wrote:
On Dec 16, 2014, at 10:40 AM, Jeremy Stanley fu...@yuggoth.org wrote:
The way I see it, we're all volunteers. We voluntarily work on free
software and associated support infrastructure. Some of us are
simply lucky enough to
On 16/12/2014 12:02, Marius Gedminas wrote:
Is there something I’m not aware that is broken currently? I thought the
transition was going pretty smoothly overall considering that a core piece
of code inside of setuptools was touched.
~80 zope.* test builds are currently failing, for mysterious
On 17 December 2014 at 09:42, Donald Stufft don...@stufft.io wrote:
Note that as of now Openstack has decided on a different path and currently
does not need any adjustments to PEP 440 as I had talked about with you, so
as of right now the only thing I really have to change (unless they change
Donald Stufft schreef op 17-12-14 02:49:
Another thing though, what you probably want to do is something like
1.1.dev0+internal1, which will sort as older than 1.1 whenever it is actually
released.
Sounds like the reasonable way to go.
Let me try, with a pip that has your local version
On Wed, Dec 17, 2014 at 10:09:56AM +, Chris Withers wrote:
FWIW, I've also been seeing failures in all of my buildout-based
library testing Jenkins jobs:
This one only on Windows and Python 2.7 only, NOT Python 2.6:
C:\Jenkins\workspace\checker-buildout\aeb5917bC:\Python27\python.exe
On 17 December 2014 at 13:31, Ethan Furman et...@stoneleaf.us wrote:
Oh, to be clear: There are no guarantees that 1.4 actually includes the
bug-fixes in +debian1, correct? It's just a
big hope?
Correct. The local versions were mostly added such that Linux distros
could indicate to Python
Maurits van Rees schreef op 17-12-14 01:46:
Maurits van Rees schreef op 17-12-14 00:53:
I have created a very basic python project called 'myproject'. It
does nothing. I have released a few versions here:
http://pypi.zestsoftware.nl/public/packagingtest/
I have now also distributed
Maurits van Rees schreef op 17-12-14 13:07:
Babel and buildout
--
With the earlier given buildout, I added an extra directory to the
find-links:
find-links = http://pypi.zestsoftware.nl/public/packagingtest/
http://pypi.zestsoftware.nl/public/
Then I updated the Babel version
I've just released version 0.2.0 of distlib on PyPI [1]. For newcomers,
distlib is a library of packaging functionality which is intended to be
usable as the basis for third-party packaging tools.
The main changes in this release are as follows:
Updated match_hostname to use the latest
On Dec 16, 2014, at 2:51 PM, Paul Moore p.f.mo...@gmail.com wrote:
On 16 December 2014 at 17:56, Donald Stufft don...@stufft.io wrote:
I’ve had a number of people complain that PEP 440 normalizes a release
candidate as 1.0c1 instead of 1.0rc1. Do we want to ammend the PEP to switch
the
On Dec 17, 2014, at 8:55 PM, Donald Stufft don...@stufft.io wrote:
On Dec 16, 2014, at 2:51 PM, Paul Moore p.f.mo...@gmail.com wrote:
On 16 December 2014 at 17:56, Donald Stufft don...@stufft.io wrote:
I’ve had a number of people complain that PEP 440 normalizes a release
candidate as
On 18 December 2014 at 11:55, Donald Stufft don...@stufft.io wrote:
On Dec 16, 2014, at 2:51 PM, Paul Moore p.f.mo...@gmail.com wrote:
On 16 December 2014 at 17:56, Donald Stufft don...@stufft.io wrote:
I’ve had a number of people complain that PEP 440 normalizes a release
candidate as 1.0c1
13 matches
Mail list logo
