At 03:03 AM 4/23/2009 +, Chad wrote:
I feel that the above is a bug. '.' should be treated as a path not a package
name, since '.' is not a valid package name.
Actually, it is.
i haven't looked at the code yet,
but it seems that a regular expression should be able to determine between
New submission from Chad :
1) easy_install can be used to install "extra" dependencies, using the following
syntax (undocumented on the PEAK website, as far as i can tell):
$ easy_install mypackage[extraFeature]
where "extraFeature" is a feature specified by the package's extras_require
keyword
At 04:52 PM 4/22/2009 +0200, Lennart Regebro wrote:
On Wed, Apr 22, 2009 at 16:18, P.J. Eby wrote:
> Er, no. It only means that you need Python 2 to be installed
*while porting
> a package* to Python 3.
No. It means it needs to be installed when installing the package from
a source distribut
On Wed, Apr 22, 2009 at 16:18, P.J. Eby wrote:
> Er, no. It only means that you need Python 2 to be installed *while porting
> a package* to Python 3.
No. It means it needs to be installed when installing the package from
a source distribution. Which is the normal way of distributing
modules.
-
At 11:12 AM 4/22/2009 +0200, Tarek Ziadé wrote:
Hi,
We worked during Pycon on version comparisons. Distutils has one but
it is a bit strict, setuptools has another one, but it's a bit
heuristic.
We would like to propose the inclusion for Python 2.7 of a new version
comparison algorithm, based o
At 08:27 AM 4/22/2009 +0200, Lennart Regebro wrote:
On Tue, Apr 21, 2009 at 19:57, P.J. Eby wrote:
> At 04:06 PM 4/21/2009 +0200, Lennart Regebro wrote:
>>
>> On Tue, Apr 21, 2009 at 15:03, P.J. Eby wrote:
>> > python2 setup.py 2to3 test
>>
>> Well, yes, but it should be
>>
>> python 3 setup
On Wed, 22 Apr 2009 11:12:22 +0200, Tarek Ziadé wrote:
Hi,
We worked during Pycon on version comparisons. Distutils has one but
it is a bit strict, setuptools has another one, but it's a bit
heuristic.
We would like to propose the inclusion for Python 2.7 of a new version
comparison algorithm,
> Maybe we could ask someone at the FSF so we have the best versions in
> our Trove classifier.
There is a list [1] of OSI approved licenses. Maybe it could be useful for the
trove classifier.
-
Carlos Tejo Alonso
Research & Development Department
CTIC Foundat
Zooko O'Whielacronx wrote:
> On Apr 21, 2009, at 18:54 PM, David Cournapeau wrote:
>
>> The problem with a new "Distutils2" 100 % compatible with the current
>> one is that it is impossible to do without recreating all the things
>> which it does wrong,
>
> I'm sorry, I was unclear. I do not think
On Apr 21, 2009, at 18:54 PM, David Cournapeau wrote:
The problem with a new "Distutils2" 100 % compatible with the current
one is that it is impossible to do without recreating all the things
which it does wrong,
I'm sorry, I was unclear. I do not think that it is super important
for a pro
On Tue, Apr 21, 2009 at 4:06 PM, Paul Moore wrote:
>
> One concrete point - The categories on the wiki don't really give me
> much help in knowing where to put my use case. I'm a user of Python
> packages - all I care about is running the installer, or if I must
> typing python setup.py bdist_wini
Hi,
We worked during Pycon on version comparisons. Distutils has one but
it is a bit strict, setuptools has another one, but it's a bit
heuristic.
We would like to propose the inclusion for Python 2.7 of a new version
comparison algorithm, based on the discussion
Fedora, Ubuntu and Python people
On Wed, 22 Apr 2009 10:42:29 +0200, Tarek Ziadé
wrote:
> There's no explicit way at distutils level to point things like
> documentation,
Well I thank you for the answer. At least I have an answer from an expert..
> maybe that could be a metadata.
>
> Maybe you can propose this, by commentin
On Wed, Apr 22, 2009 at 2:49 AM, David Lyon wrote:
>
> Hi All,
>
> Once a package is installed on a system... is there any way to find out
> where it was installed to?
Not at the moment. PEP 376 though, proposes a new API to be able to reach
the metadata of an installed package, browsing the dire
14 matches
Mail list logo