On Fri, Oct 16, 2009 at 3:39 AM, sstein...@gmail.com
sstein...@gmail.com wrote:
Some of the files (e.g. setuptools/archive_util.py) are only different by a
bit of whitespace.
archive_util, in the mid term (2.7/3.2) will dissapear, in favor of
changes in Distutils side.
In taking a closer
Hey
While we are working at fixing bugs in 0.6.x, I would like to organize
a first online coding sprint for the 0.7.x series,
goals:
- finalize the first splitting version
- define a more detailed roadmap for each splitted package
- build a better test environment (see if we can set up a
I think it is confusing that
easy_install blah
doesn't do anything, and doesn't provide any clue, if it was to do an
update. You need to say
easy_install -U blah
There are a few choices here. One might be that
easy_install blah
could notify you that an update is available.
Personally, my
2009/10/16 Neal Becker ndbeck...@gmail.com:
I think it is confusing that
easy_install blah
doesn't do anything, and doesn't provide any clue, if it was to do an
update.
Was to do? It doesn't know that there is an update available, unless
you ask it to check. It does tell you that it's
Hey,
Marc-André Lemburg gave me a key points about the static metadata
discussions we have (wether its PEP 390 or around it)
He said that the important thing was to have the context-dependant
markers in PKG-INFO, and that having in described in
setup.cfg or in setup.py by any way is not the
On Fri, Oct 16, 2009 at 4:46 PM, Tres Seaver tsea...@palladion.com wrote:
Shouldn't this point at PEP 345, which already defines a metadata
version 1.2?
Right sorry, I messed up with the PEPs numbers. PEP 314 is the final
1.1, and PEP 345 is the draft for 1.2, where we should work to change
At 10:46 AM 10/16/2009 -0400, sstein...@gmail.com wrote:
I don't know that I'd call what I saw designed. Complex, yes, but
design implies a plan and known direction, communicated by design
documents with tests that prove the code is working as expected.
This is not designed by any objective
On Oct 16, 2009, at 11:41 AM, P.J. Eby wrote:
At 10:46 AM 10/16/2009 -0400, sstein...@gmail.com wrote:
I don't know that I'd call what I saw designed. Complex, yes, but
design implies a plan and known direction, communicated by design
documents with tests that prove the code is working as
In article hb9kte$ct...@ger.gmane.org,
Neal Becker ndbeck...@gmail.com wrote:
I think it is confusing that
easy_install blah
doesn't do anything, and doesn't provide any clue, if it was to do an
update. You need to say
easy_install -U blah
There are a few choices here. One might be
After giving it some thought, I've decided to hold off on pushing out
the 0.6c10 release until Monday morning, since it's likely that some
people have scripts or build processes that run off of ez_setup SVN
or the latest PyPI version of setuptools... and who aren't aware the
release is coming
On Oct 16, 2009, at 12:25 PM, Brandon Craig Rhodes wrote:
Jannis Leidel jan...@leidel.info writes:
That'd be very much appreciated, I'm sure the experience of the
distribute people would be helpful, too.
I'm not sure I quite approve of their approach, since it makes
installing Distribute
2009/10/16 sstein...@gmail.com sstein...@gmail.com:
Doesn't that also mean that the Python 3 version of Distribute is generated
live on the installation system?
That is absolutely true.
That doesn't seem right because that
leaves the possibility that the code generated by 2to3 is different
On Fri, Oct 16, 2009 at 6:20 AM, Neal Becker ndbeck...@gmail.com wrote:
I think it is confusing that
easy_install blah
doesn't do anything, and doesn't provide any clue, if it was to do an
update. You need to say
easy_install -U blah
There are a few choices here. One might be that
On Oct 16, 2009, at 12:59 PM, Lennart Regebro wrote:
I'm going to cross-post this to the distutils list as well. If the
idea is
to stabilize Distribute, get some tests in place, etc. then this
method of
distribution (running 2to3 in situ, as it were) is not the correct
way to
do it from
On Fri, Oct 16, 2009 at 8:54 AM, Tarek Ziadé ziade.ta...@gmail.com wrote:
Marc-André Lemburg gave me a key points about the static metadata
discussions we have (wether its PEP 390 or around it)
He said that the important thing was to have the context-dependant
markers in PKG-INFO, and that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ian Bicking wrote:
On Fri, Oct 16, 2009 at 8:54 AM, Tarek Ziadé ziade.ta...@gmail.com wrote:
Marc-André Lemburg gave me a key points about the static metadata
discussions we have (wether its PEP 390 or around it)
He said that the important thing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
sstein...@gmail.com wrote:
On Oct 16, 2009, at 12:59 PM, Lennart Regebro wrote:
I'm going to cross-post this to the distutils list as well. If the
idea is
to stabilize Distribute, get some tests in place, etc. then this
method of
On Oct 16, 2009, at 2:09 PM, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
sstein...@gmail.com wrote:
On Oct 16, 2009, at 12:59 PM, Lennart Regebro wrote:
I'm going to cross-post this to the distutils list as well. If the
idea is to stabilize Distribute, get some tests
On 06:33 pm, sstein...@gmail.com wrote:
On Oct 16, 2009, at 2:09 PM, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
sstein...@gmail.com wrote:
On Oct 16, 2009, at 12:59 PM, Lennart Regebro wrote:
I'm going to cross-post this to the distutils list as well. If the
idea is
On Oct 16, 2009, at 3:56 PM, exar...@twistedmatrix.com wrote:
Buildbots seem to be in short supply though they should be easy
enough to come by in this day and age of penny-an-hour cloud
computing.
I think I'll see if maybe I can just whip up something about this...
Not sure if you're
On Fri, 16 Oct 2009 15:54:29 +0200, Tarek Ziadé ziade.ta...@gmail.com
wrote:
But what really matters at the end is to provide a new Metadata format
where these marker are present, so any consumer
can play with them (and Distutils provide an API to play with them :
the DistributionMetadata
I've just downloaded and configured the Distribute buildbot and it
appears that a dependency is missing somewhere. I get this (just the
errors excerpted).
Just wanted to capture this before I figure out what needs to be done...
test_make_tarball
Looks like you're using a build of Python that wasn't compiled with
zlib support (--with-zlib, IIRC).
2009/10/16 sstein...@gmail.com sstein...@gmail.com:
I've just downloaded and configured the Distribute buildbot and it appears
that a dependency is missing somewhere. I get this (just the
On Oct 16, 2009, at 6:58 PM, Nathan Yergler wrote:
Looks like you're using a build of Python that wasn't compiled with
zlib support (--with-zlib, IIRC).
Right -- that's the python that the buildbot compiled from source,
that's why it's a bug ;-).
S
On Sat, Oct 17, 2009 at 12:58 AM, Nathan Yergler
nat...@creativecommons.org wrote:
Looks like you're using a build of Python that wasn't compiled with
zlib support (--with-zlib, IIRC).
2009/10/16 sstein...@gmail.com sstein...@gmail.com:
I've just downloaded and configured the Distribute
On Fri, Oct 16, 2009 at 8:06 PM, Tres Seaver tsea...@palladion.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ian Bicking wrote:
On Fri, Oct 16, 2009 at 8:54 AM, Tarek Ziadé ziade.ta...@gmail.com wrote:
Marc-André Lemburg gave me a key points about the static metadata
discussions
On Oct 16, 2009, at 7:04 PM, Tarek Ziadé wrote:
On Sat, Oct 17, 2009 at 12:58 AM, Nathan Yergler
nat...@creativecommons.org wrote:
Looks like you're using a build of Python that wasn't compiled with
zlib support (--with-zlib, IIRC).
2009/10/16 sstein...@gmail.com sstein...@gmail.com:
I've
On Sat, Oct 17, 2009 at 12:39 AM, David Lyon david.l...@preisshare.net wrote:
Requires: (linux-suse-kde-64) foo
How this expression would be verified on the target system ?
Regards
Tarek
___
Distutils-SIG maillist - Distutils-SIG@python.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
sstein...@gmail.com wrote:
On Oct 16, 2009, at 6:58 PM, Nathan Yergler wrote:
Looks like you're using a build of Python that wasn't compiled with
zlib support (--with-zlib, IIRC).
Right -- that's the python that the buildbot compiled from
On Sat, Oct 17, 2009 at 1:13 AM, sstein...@gmail.com
sstein...@gmail.com wrote:
On Oct 16, 2009, at 7:04 PM, Tarek Ziadé wrote:
On Sat, Oct 17, 2009 at 12:58 AM, Nathan Yergler
nat...@creativecommons.org wrote:
Looks like you're using a build of Python that wasn't compiled with
zlib
On Sat, Oct 17, 2009 at 1:21 AM, Tarek Ziadé ziade.ta...@gmail.com wrote:
IOW the way python is built in the bbot, is now using your system's
zlib support...
Arggg... I am the typo master...
s/now/not.
So as Tres said maybe Ubuntu ships with a Python with zlib support,
but doesn't provide
On Oct 16, 2009, at 7:21 PM, Tarek Ziadé wrote:
On Sat, Oct 17, 2009 at 1:13 AM, sstein...@gmail.com
sstein...@gmail.com wrote:
On Oct 16, 2009, at 7:04 PM, Tarek Ziadé wrote:
On Sat, Oct 17, 2009 at 12:58 AM, Nathan Yergler
nat...@creativecommons.org wrote:
Looks like you're using a
On Oct 16, 2009, at 7:26 PM, Tarek Ziadé wrote:
On Sat, Oct 17, 2009 at 1:21 AM, Tarek Ziadé ziade.ta...@gmail.com
wrote:
IOW the way python is built in the bbot, is now using your system's
zlib support...
Arggg... I am the typo master...
s/now/not.
So as Tres said maybe Ubuntu ships
On Sat, 17 Oct 2009 01:15:25 +0200, Tarek Ziadé ziade.ta...@gmail.com
wrote:
On Sat, Oct 17, 2009 at 12:39 AM, David Lyon david.l...@preisshare.net
wrote:
Requires: (linux-suse-kde-64) foo
How this expression would be verified on the target system ?
I'm working on coding it. Basically the
On Sat, Oct 17, 2009 at 1:38 AM, David Lyon david.l...@preisshare.net wrote:
# -- See what our platform is
def build_platform_bit_map():
if sys.platform == 'darwin':
self.platform_bits['mac'] = True
# -- Further sub-bit determination
..
else
On Sat, Oct 17, 2009 at 1:39 AM, sstein...@gmail.com
sstein...@gmail.com wrote:
On Oct 16, 2009, at 7:26 PM, Tarek Ziadé wrote:
On Sat, Oct 17, 2009 at 1:21 AM, Tarek Ziadé ziade.ta...@gmail.com
wrote:
IOW the way python is built in the bbot, is now using your system's
zlib support...
On Oct 16, 2009, at 7:57 PM, Tarek Ziadé wrote:
On Sat, Oct 17, 2009 at 1:39 AM, sstein...@gmail.com
sstein...@gmail.com wrote:
On Oct 16, 2009, at 7:26 PM, Tarek Ziadé wrote:
On Sat, Oct 17, 2009 at 1:21 AM, Tarek Ziadé ziade.ta...@gmail.com
wrote:
IOW the way python is built in the
On 2009-10-16, P.J. Eby p...@telecommunity.com wrote:
At 10:46 AM 10/16/2009 -0400, sstein...@gmail.com wrote:
This is not designed by any objective standard I'd use.
You are correct; setuptools itself was not particularly
designed. Eggs are, entry points are, a few other odds and ends were
On Oct 16, 2009, at 8:10 PM, Reinout van Rees wrote:
On 2009-10-16, P.J. Eby p...@telecommunity.com wrote:
At 10:46 AM 10/16/2009 -0400, sstein...@gmail.com wrote:
This is not designed by any objective standard I'd use.
You are correct; setuptools itself was not particularly
designed.
On Sat, 17 Oct 2009 01:53:48 +0200, Tarek Ziadé ziade.ta...@gmail.com
wrote:
So far.. so good. It's basically what we proposed earlier in PEP 390, but
for
the distribution, the desktop (kde, etc)...
..
That would require a new
stdlib module that would be very hard to implement and maintain
On 2009-10-16, P.J. Eby p...@telecommunity.com wrote:
Also, this will give those who are using Distribute and do *not* wish
to use this release, a chance to upgrade to the latest version of
Distribute first. (Which, if I understand correctly, includes code
to prevent accidental
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
sstein...@gmail.com wrote:
On Oct 16, 2009, at 7:26 PM, Tarek Ziadé wrote:
So as Tres said maybe Ubuntu ships with a Python with zlib support,
but doesn't provide zlib headers.
Ok, so the python you build from the trunk checkout doesn't have
42 matches
Mail list logo
