Hi guys,
Just thought I'd might provide this script to fellow developers
which fixes .pth files (easy-install.pth / .egg was the prime target
-- see the comments for more details):
http://yaneurabeya.livejournal.com/3929.html.
Comments are more than welcome. If I get any, I'll try to get
At 02:43 AM 5/4/2009 -0700, Garrett Cooper wrote:
Hi guys,
Just thought I'd might provide this script to fellow developers
which fixes .pth files (easy-install.pth / .egg was the prime target
-- see the comments for more details):
http://yaneurabeya.livejournal.com/3929.html.
Comments
There's another point I was thinking about in PEP 376
What about dropping the 'egg' part in 'PROJECT.egg-info' ? and replace it with
'PROJECT.info'
(and make the 2.7 version compatible with PROJECT.egg-info )
I know it's a minor change, but it seems that a lot of people are
confused with
At 05:23 PM 5/4/2009 +0200, Tarek Ziadé wrote:
There's another point I was thinking about in PEP 376
What about dropping the 'egg' part in 'PROJECT.egg-info' ? and
replace it with
'PROJECT.info'
(and make the 2.7 version compatible with PROJECT.egg-info )
I know it's a minor change,
At 07:34 PM 5/3/2009 +0200, Tarek Ziadé wrote:
2009/5/3 P.J. Eby p...@telecommunity.com:
At 12:03 PM 5/3/2009 +0200, Tarek Ziadé wrote:
The name of each file will have to be normalized: all upper case with
no extensions.
Any opinions ?
I don't see any point to the normalization.
To
2009/5/4 P.J. Eby p...@telecommunity.com:
At 05:23 PM 5/4/2009 +0200, Tarek Ziadé wrote:
There's another point I was thinking about in PEP 376
What about dropping the 'egg' part in 'PROJECT.egg-info' ? and replace it
with
'PROJECT.info'
(and make the 2.7 version compatible with
On Mon, May 4, 2009 at 5:48 PM, P.J. Eby p...@telecommunity.com wrote:
I don't see any point to the normalization.
To avoid different naming conventions like:
PKG-INFO, requires.txt, SOURCES.txt
And the problem with that is...?
inconsistency, but right, it makes no sense if any file/dir
On Mon, May 04, 2009 at 05:54:59PM +0200, Tarek Ziadé wrote:
2009/5/4 P.J. Eby p...@telecommunity.com:
At 05:23 PM 5/4/2009 +0200, Tarek Ziadé wrote:
There's another point I was thinking about in PEP 376
What about dropping the 'egg' part in 'PROJECT.egg-info' ? and replace it
with
On Mon, May 4, 2009 at 6:12 PM, Floris Bruynooghe
floris.bruynoo...@gmail.com wrote:
But what about the idea ?
How can we be sure that we won't want to change it again in the
future?
well I think it's now or never, since we are defining a standard here
for this directory.
As for
At 05:54 PM 5/4/2009 +0200, Tarek Ziadé wrote:
2009/5/4 P.J. Eby p...@telecommunity.com:
At 05:23 PM 5/4/2009 +0200, Tarek Ziadé wrote:
There's another point I was thinking about in PEP 376
What about dropping the 'egg' part in 'PROJECT.egg-info' ? and replace it
with
'PROJECT.info'
At 06:31 PM 5/4/2009 +0200, Tarek Ziadé wrote:
Ok then, we will have to provide extra documentation to make people
understand that the '.egg-info' directory has absolutely nothing to do
with egg-the-format
but is rather a metadata container.
On the contrary; .egg-info *is* an egg format; see
Tarek Ziadé wrote:
On Mon, May 4, 2009 at 6:12 PM, Floris Bruynooghe
floris.bruynoo...@gmail.com wrote:
Ok then, we will have to provide extra documentation to make people
understand that the '.egg-info' directory has absolutely nothing to do
with egg-the-format
but is rather a metadata
On Mon, May 4, 2009 at 11:31 AM, Tarek Ziadé ziade.ta...@gmail.com wrote:
Ok then, we will have to provide extra documentation to make people
understand that the '.egg-info' directory has absolutely nothing to do
with egg-the-format
but is rather a metadata container.
'egg-info' was
Hi P.J.!
On Mon, May 4, 2009 at 8:20 AM, P.J. Eby p...@telecommunity.com wrote:
At 02:43 AM 5/4/2009 -0700, Garrett Cooper wrote:
Hi guys,
Just thought I'd might provide this script to fellow developers
which fixes .pth files (easy-install.pth / .egg was the prime target
-- see the
On Mon, May 4, 2009 at 1:11 PM, Garrett Cooper yaneg...@gmail.com wrote:
Hi P.J.!
On Mon, May 4, 2009 at 8:20 AM, P.J. Eby p...@telecommunity.com wrote:
At 02:43 AM 5/4/2009 -0700, Garrett Cooper wrote:
Hi guys,
Just thought I'd might provide this script to fellow developers
which fixes
At 01:11 PM 5/4/2009 -0700, Garrett Cooper wrote:
You're right -- it doesn't protect against the following ():
/full/path/to/package.egg
./package.egg
By duplicates, I meant 'package-1.0.egg' and 'package-1.1.egg', not
alternate paths to the same file.
(As for the '.' replacement, you
2009/5/4 P.J. Eby p...@telecommunity.com:
At 06:31 PM 5/4/2009 +0200, Tarek Ziadé wrote:
Ok then, we will have to provide extra documentation to make people
understand that the '.egg-info' directory has absolutely nothing to do
with egg-the-format
but is rather a metadata container.
On the
On Mon, May 4, 2009 at 7:43 PM, Ian Bicking i...@colorstudy.com wrote:
On Mon, May 4, 2009 at 11:31 AM, Tarek Ziadé ziade.ta...@gmail.com wrote:
Ok then, we will have to provide extra documentation to make people
understand that the '.egg-info' directory has absolutely nothing to do
with
On Mon, May 4, 2009 at 7:51 PM, P.J. Eby p...@telecommunity.com wrote:
At 06:01 PM 5/4/2009 +0200, Tarek Ziadé wrote:
On Mon, May 4, 2009 at 5:48 PM, P.J. Eby p...@telecommunity.com wrote:
I don't see any point to the normalization.
To avoid different naming conventions like:
On Mon, May 4, 2009 at 7:42 PM, Hanno Schlichting hanno...@hannosch.eu wrote:
Tarek Ziadé wrote:
On Mon, May 4, 2009 at 6:12 PM, Floris Bruynooghe
floris.bruynoo...@gmail.com wrote:
Ok then, we will have to provide extra documentation to make people
understand that the '.egg-info' directory
At 12:50 AM 5/5/2009 +0200, Tarek Ziadé wrote:
On Mon, May 4, 2009 at 7:51 PM, P.J. Eby p...@telecommunity.com wrote:
At 06:01 PM 5/4/2009 +0200, Tarek Ziadé wrote:
On Mon, May 4, 2009 at 5:48 PM, P.J. Eby p...@telecommunity.com wrote:
I don't see any point to the normalization.
To
2009/5/3 P.J. Eby p...@telecommunity.com:
At 12:03 PM 5/3/2009 +0200, Tarek Ziadé wrote:
The name of each file will have to be normalized: all upper case with
no extensions.
Any opinions ?
I don't see any point to the normalization. However, being able to install
arbitrary files in
Hello
I am making a separate email for this topic to make sure no one misses it.
There are *many* benefits of adding entry points into Distutils. In
fact, adding a plugin system in there,
will help make the commands more extendable and therefore will help us
in the long term to remove things
out
Hi Tarek,
On Tue, 5 May 2009 01:37:34 +0200, Tarek Ziadé ziade.ta...@gmail.com
wrote:
Furtermore, if we provide the ability to fill egg-info with third
party packages registered through
a plugin system, it make sense to prepare it at packaging time to
avoid having to install this third
On Tue, 5 May 2009 01:46:21 +0200, Tarek Ziadé ziade.ta...@gmail.com
wrote:
Hello
I am making a separate email for this topic to make sure no one misses
it.
There are *many* benefits of adding entry points into Distutils. In
fact, adding a plugin system in there,
will help make the
On Tue, May 5, 2009 at 1:47 AM, David Lyon david.l...@preisshare.net wrote:
Hi Tarek,
On Tue, 5 May 2009 01:37:34 +0200, Tarek Ziadé ziade.ta...@gmail.com
wrote:
Furtermore, if we provide the ability to fill egg-info with third
party packages registered through
a plugin system, it make
On Tue, 5 May 2009 01:58:57 +0200, Tarek Ziadé ziade.ta...@gmail.com
wrote:
That is what entry points are providing : the ability to mark a code
locate anywhere in your installation
and to load it when needed in your execution context.
ok - but don't we already have this in site.py ? inside
On Tue, May 5, 2009 at 2:00 AM, David Lyon david.l...@preisshare.net wrote:
On Tue, 5 May 2009 01:58:57 +0200, Tarek Ziadé ziade.ta...@gmail.com
wrote:
That is what entry points are providing : the ability to mark a code
locate anywhere in your installation
and to load it when needed in
On Tue, 5 May 2009 02:11:36 +0200, Tarek Ziadé ziade.ta...@gmail.com
wrote:
I am not sure to understand what you are explaining - when the python
interpreter starts up, it doesn't load every installed package
in memory. the loading happens when you do import foo
Correct. I didn't say it
At 06:57 PM 5/4/2009 -0500, Ian Bicking wrote:
* I'm uncomfortable with the way entry points are scanned. I
haven't looked close enough to back it up with numbers, but I think
there's a noticeable performance degradation when the number of
installed packages becomes large. (Given the
Tarek Ziadé ziade.ta...@gmail.com writes:
There are *many* benefits of adding entry points into Distutils. In
fact, adding a plugin system in there, will help make the commands
more extendable and therefore will help us in the long term to remove
things out of Distutils.
I don't see what
On Mon, May 4, 2009 at 1:46 PM, P.J. Eby p...@telecommunity.com wrote:
At 01:11 PM 5/4/2009 -0700, Garrett Cooper wrote:
You're right -- it doesn't protect against the following ():
/full/path/to/package.egg
./package.egg
By duplicates, I meant 'package-1.0.egg' and 'package-1.1.egg', not
32 matches
Mail list logo
