On 2009-09-05, Zooko Wilcox-O'Hearn wrote:
> On Wednesday,2009-09-02, at 7:07 , Reinout van Rees wrote:
>
>> First things first: what I want to accomplish is to install
>> pyflakes and docutils in a buildout. That is, I want to have a bin/
>> pyflakes and bin/rst2* scripts.
>
> See also
>
> ht
On 2009-09-04, P.J. Eby wrote:
> At 09:30 PM 9/4/2009 +, Reinout van Rees wrote:
>>There's one thing I couldn't find out: does the zipfile module report
>>filenames as slashes or does it use the OS's preference? /me has no windows
>>around to test it on. So there might be an OS inconsistency
On Wednesday,2009-09-02, at 7:07 , Reinout van Rees wrote:
First things first: what I want to accomplish is to install
pyflakes and docutils in a buildout. That is, I want to have a bin/
pyflakes and bin/rst2* scripts.
See also
http://pypi.python.org/pypi/setuptools_pyflakes
Which adds a
At 09:30 PM 9/4/2009 +, Reinout van Rees wrote:
There's one thing I couldn't find out: does the zipfile module report
filenames as slashes or does it use the OS's preference? /me has no windows
around to test it on. So there might be an OS inconsistency there. Running
the tests on windows
At 12:05 PM 9/4/2009 +, Reinout van Rees wrote:
On 2009-09-04, P.J. Eby wrote:
> At 01:58 PM 9/3/2009 -0400, Jim Fulton wrote:
>>I think the script information should be included somehow so that it
>>can be gotten from eggs.
>
> The original script files get stored in the "EGG-INFO/scripts"
On 2009-09-04, Jim Fulton wrote:
>> I verified that it doesn't work with zipped eggs. Are there alternatives for
>> getting my hand on that listdir of EGG-INFO/scripts/* without unzipping the
>> egg? Otherwise I'm in favour of just leaving zipped eggs be.
>
> Sure, use the zipfile module.
Hm.
On Fri, Sep 4, 2009 at 11:35 AM, Reinout van Rees wrote:
> On 2009-09-04, Reinout van Rees wrote:
>> On 2009-09-04, P.J. Eby wrote:
>>> At 01:58 PM 9/3/2009 -0400, Jim Fulton wrote:
I think the script information should be included somehow so that it
can be gotten from eggs.
>>>
>>> The o
On Fri, Sep 4, 2009 at 5:35 PM, Reinout van Rees wrote:
> On 2009-09-04, Reinout van Rees wrote:
>> On 2009-09-04, P.J. Eby wrote:
>>> At 01:58 PM 9/3/2009 -0400, Jim Fulton wrote:
I think the script information should be included somehow so that it
can be gotten from eggs.
>>>
>>> The or
On 2009-09-04, Reinout van Rees wrote:
> On 2009-09-04, P.J. Eby wrote:
>> At 01:58 PM 9/3/2009 -0400, Jim Fulton wrote:
>>>I think the script information should be included somehow so that it
>>>can be gotten from eggs.
>>
>> The original script files get stored in the "EGG-INFO/scripts" directo
On 2009-09-04, P.J. Eby wrote:
> At 01:58 PM 9/3/2009 -0400, Jim Fulton wrote:
>>I think the script information should be included somehow so that it
>>can be gotten from eggs.
>
> The original script files get stored in the "EGG-INFO/scripts" directory.
Ok, I got something working based on that
At 01:58 PM 9/3/2009 -0400, Jim Fulton wrote:
I think the script information should be included somehow so that it
can be gotten from eggs.
The original script files get stored in the "EGG-INFO/scripts" directory.
___
Distutils-SIG maillist - Distu
On Thu, Sep 3, 2009 at 12:34 PM, Tarek Ziadé wrote:
> On Wed, Sep 2, 2009 at 7:50 PM, Jim Fulton wrote:
>>
>> Yeah, it's too bad that the meta data is lost. It amazes me how
>> willing distutils and setuptools are to toss meta data passed to
>> setup.
>
> Are your referring to the Package Metadata
On Wed, Sep 2, 2009 at 7:50 PM, Jim Fulton wrote:
>
> Yeah, it's too bad that the meta data is lost. It amazes me how
> willing distutils and setuptools are to toss meta data passed to
> setup.
Are your referring to the Package Metadata ? (eg the PEP 314 that
lands in the PKG-INFO)
'scripts' is
On Thu, Sep 3, 2009 at 11:46 AM, Reinout van Rees wrote:
> On 2009-09-02, Jim Fulton wrote:
>>
>> Note that, as Tarek reminded us, buildout lets you define entry points
>> yourself. In fact, I happen to have done this for pyflakes myself a
>> couple of weeks ago:
>>
>> [pyflakes]
>> recipe = z
On 2009-09-02, Jim Fulton wrote:
>
> Note that, as Tarek reminded us, buildout lets you define entry points
> yourself. In fact, I happen to have done this for pyflakes myself a
> couple of weeks ago:
>
> [pyflakes]
> recipe = zc.recipe.egg
> eggs = pyflakes
> entry-points = pyflakes=pyfla
On Wed, Sep 2, 2009 at 9:07 AM, Reinout van Rees wrote:
> First things first: what I want to accomplish is to install pyflakes and
> docutils in a buildout. That is, I want to have a bin/pyflakes and bin/rst2*
> scripts.
>
> - Buildout listens to the console_scripts entry point.
>
> - pyflakes and
On 2009-09-02, Reinout van Rees wrote:
> - pyflakes and docutils use the (apparently old) scripts=['scripts/pyflakes']
> option instead of a console_scripts entry point.
Just for easy reference: here's the setup.py of pyflakes:
#!/usr/bin/python
# (c) 2005-2009 Divmod, Inc. See LICENSE file
On Wed, Sep 2, 2009 at 3:07 PM, Reinout van Rees wrote:
> First things first: what I want to accomplish is to install pyflakes and
> docutils in a buildout. That is, I want to have a bin/pyflakes and bin/rst2*
> scripts.
>
> - Buildout listens to the console_scripts entry point.
>
> - pyflakes and
First things first: what I want to accomplish is to install pyflakes and
docutils in a buildout. That is, I want to have a bin/pyflakes and bin/rst2*
scripts.
- Buildout listens to the console_scripts entry point.
- pyflakes and docutils use the (apparently old) scripts=['scripts/pyflakes']
op
19 matches
Mail list logo
