2009/5/14 P.J. Eby p...@telecommunity.com:
At 02:34 PM 5/13/2009 +0200, Tarek Ziadé wrote:
Any feedback on this dev version of post release use case
It looks like the 'suggest' function doesn't handle svn revisions properly
Ok I'll check that
To be clear, I'm not opposed to blessing a
2009/5/14 P.J. Eby p...@telecommunity.com:
At 02:34 PM 5/13/2009 +0200, Tarek Ziadé wrote:
Any feedback on this dev version of post release use case
It looks like the 'suggest' function doesn't handle svn revisions properly
for conversion from setuptools versions. Setuptools '-r###' is a
Hello
for PEP 376, I have one last fuzzy point.
http://svn.python.org/view/peps/trunk/pep-0376.txt?view=markup
The get_egg_info api is currently based on scanning the whole
sys.path. And since sys.path can be modified by people,
so the algorithm is linear and can slow down when there are a lot
On Thu, May 14, 2009 at 12:33 PM, Noah Gift noah.g...@gmail.com wrote:
One thing that isn't clear to me is whether this could then lead to a
potentially new third party packaging system, or library, that will just do
the same thing again, and create a linear scanning algorithm. Is there a
way
New submission from mkesper mkes...@schokokeks.org:
If you want to install 0.6c9 on windows, you face a hen-and-egg-Problem:
An .eeg exists, but no installer.
--
messages: 287
nosy: mkesper
priority: feature
status: unread
title: No 2.6 install setup
2009/5/14 Tarek Ziadé ziade.ta...@gmail.com:
I'd like to make a difference between what is importable and what is
installed in Python.
what's installed for me is what is in a site-packages directory that
contains egg-info directories.
I'm not sure how well-defined that is. Can you precisely
On Thu, 14 May 2009 12:03:21 +0200, Tarek Ziadé ziade.ta...@gmail.com
wrote:
I have a proposal: let's restrict the search for this API to
site-package directories only. (directories added with
site.addsitedir)
People will be able to mark add any directory (like the per-user
site-package
On Thu, 14 May 2009 14:38:33 +0200, Tarek Ziadé ziade.ta...@gmail.com
wrote:
When a program is launched, the site-packages places should be limited
to:
- the python site-packages (wether is central, wether it's local,
using virtualenv)
- the per user site-packages (PEP 370)
- maybe a third
2009/5/14 David Lyon david.l...@preisshare.net:
On Thu, 14 May 2009 14:38:07 +0100, Paul Moore p.f.mo...@gmail.com wrote:
2009/5/14 Tarek Ziadé ziade.ta...@gmail.com:
I'm not sure how well-defined that is. Can you precisely define what a
site-packages directory is?
Site-packages is
On Thu, 14 May 2009 16:01:55 +0100, Paul Moore p.f.mo...@gmail.com wrote:
The main point here is to emphasize that there are some fairly obscure
ways for directories to end up in sys.path, even if we exclude user
code. The proposal needs to make a statement on how all such cases are
handled
At 10:56 PM 5/13/2009 -0500, Randall Smith wrote:
I'd like to bundle some third party eggs with my application without
installing them. Typically, I'd read __file__ and alter sys.path at
runtime to include the third party packages, but I understand that
will not work with zipped eggs.
I
At 10:59 AM 5/14/2009 +0200, Tarek Ziadé wrote:
2009/5/14 P.J. Eby p...@telecommunity.com:
At 02:34 PM 5/13/2009 +0200, Tarek Ziadé wrote:
Any feedback on this dev version of post release use case
It looks like the 'suggest' function doesn't handle svn revisions properly
for conversion
At 10:19 AM 5/14/2009 +0200, Tarek Ziadé wrote:
from a setuptools user point of view, the benefit I can see is that
they will have better
version numbers
Better how? That was my question. I personally find the common
version patterns in use (e.g. '-' and '-r' for post-releases) less
On Thu, May 14, 2009 at 02:38:07PM +0100, Paul Moore wrote:
2009/5/14 Tarek Ziadé ziade.ta...@gmail.com:
I'd like to make a difference between what is importable and what is
installed in Python.
what's installed for me is what is in a site-packages directory that
contains egg-info
At 12:03 PM 5/14/2009 +0200, Tarek Ziadé wrote:
Hello
for PEP 376, I have one last fuzzy point.
http://svn.python.org/view/peps/trunk/pep-0376.txt?view=markup
The get_egg_info api is currently based on scanning the whole
sys.path. And since sys.path can be modified by people,
so the algorithm
On Thu, May 14, 2009 at 3:38 PM, Paul Moore p.f.mo...@gmail.com wrote:
2009/5/14 Tarek Ziadé ziade.ta...@gmail.com:
I'd like to make a difference between what is importable and what is
installed in Python.
what's installed for me is what is in a site-packages directory that
contains egg-info
At 11:10 PM 5/14/2009 +0200, Tarek Ziadé wrote:
2009/5/14 P.J. Eby p...@telecommunity.com:
IOW, this approach keeps simple things simple, and leaves complex things
possible. It also does less I/O than what you're proposing, since in the
normal case the directories are only ever searched
On Thu, May 14, 2009 at 11:27 PM, P.J. Eby p...@telecommunity.com wrote:
The relevant classes in pkg_resources, btw, are WorkingSet, Distribution,
and EntryPoint. You might want to just copy them and strip out the parts
you don't need. (i.e. sys.path manipulation and requirements-resolving
P.J. Eby wrote:
Yes. Simply install your entire application as eggs and scripts in a
single directory (using easy_install -maxd somedir myapp) and then
tarball and ship somedir. Less muss, less fuss, and no require().
(I.e., just declare your dependencies in setup.py)
So far, I like this.
At 11:38 PM 5/14/2009 +0200, Tarek Ziadé wrote:
That happened because I got a bit lost in the way finders were working
in setuptools, which seemed
a bit over-engineered at that time to me (but I might end up changing
my mind at sime point when I understand it better).
The finders mechanism is
On Fri, May 15, 2009 at 10:48 AM, P.J. Eby p...@telecommunity.com wrote:
At 11:38 PM 5/14/2009 +0200, Tarek Ziadé wrote:
That happened because I got a bit lost in the way finders were working
in setuptools, which seemed
a bit over-engineered at that time to me (but I might end up changing
21 matches
Mail list logo
