> Not sure if you really meant distutils, as that is part of Python itself.
Of course I meant setuptools / distribute
___
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
On Mon, Jun 25, 2012 at 8:35 PM, Daniel Holth wrote:
> OK I'll do that. Of course it also means the code won't work on Python
> < when e-mail.parser was introduced.
>
> What is the floor on Python versions for distutils?
distribute and setuptools try to support Python >= 2.3 - though the
earlier
OK I'll do that. Of course it also means the code won't work on Python
< when e-mail.parser was introduced.
What is the floor on Python versions for distutils? Would it work to
require Python 2.6 just for the .dist-info bits?
___
Distutils-SIG maillist
The prose isn't PEP-compliant yet, but here is my whole proposal for
adding extras to .dist-info-style / Metadata 1.2 distributions.
An 'extra' is an optional feature that can augment a distribution's
requirements. An extra name must be a valid Python identifier and is
referenced using subscript
On 6/25/12 12:57 PM, Jim Fulton wrote:
On Mon, Jun 25, 2012 at 2:53 AM, Tarek Ziadé wrote:
On 6/25/12 1:11 AM, Jim Fulton wrote:
https://bitbucket.org/tarek/distribute/issue/289/distribute-broken-with-python-33
I'm gonna try to work around it in buildout 2 by monkey-patching
distribute.
Jim
On Mon, Jun 25, 2012 at 3:53 AM, mbogosian wrote:
>
> Perhaps I have misunderstood the intended behavior, but I thought one
> should be able to do this:
>
> % easy_install BeautifulSoup==3.0.8
> ...
> % easy_install -U BeautifulSoup
> [installs 3.1.0.1]
> ...
> % python -c 'import pkg_resources ;
On 25-06-12 13:49, Hanno Schlichting wrote:
On Mon, Jun 25, 2012 at 1:44 PM, Reinout van Rees wrote:
warning: sdist: standard file not found: should have one of README,
README.txt
The reason for the missing file is that it is called README.rst now because
bitbucket and github pick up that exte
On Mon, Jun 25, 2012 at 1:44 PM, Reinout van Rees wrote:
> warning: sdist: standard file not found: should have one of README,
> README.txt
>
> The reason for the missing file is that it is called README.rst now because
> bitbucket and github pick up that extension. Is there something that can be
Hi,
I often get warnings like:
warning: sdist: standard file not found: should have one of README,
README.txt
The reason for the missing file is that it is called README.rst now
because bitbucket and github pick up that extension. Is there something
that can be done about this warning?
(
On Mon, Jun 25, 2012 at 2:53 AM, Tarek Ziadé wrote:
> On 6/25/12 1:11 AM, Jim Fulton wrote:
>>
>>
>> https://bitbucket.org/tarek/distribute/issue/289/distribute-broken-with-python-33
>>
>> I'm gonna try to work around it in buildout 2 by monkey-patching
>> distribute.
>>
>> Jim
>>
> If you write t
New submission from mbogosian :
Perhaps I have misunderstood the intended behavior, but I thought one should be
able to do this:
- - - - - - - - %< - - - - - - - -
% easy_install BeautifulSoup==3.0.8
...
% easy_install -U BeautifulSoup
[installs 3.1.0.1]
...
% python -c 'import pkg_resources ;
11 matches
Mail list logo
