On Wed, Feb 20, 2013 at 10:18 AM, Daniel Holth wrote:
> Wheel is only defined for 1 dist per archive.
Indeed. We did briefly discuss the idea of wheels-within-wheels
somewhere along the line (it may even have been a private email
conversation I had with Daniel about an early version of the wheel
Marcus Smith gmail.com> writes:
> when I run "wheeler.py pyramid" (after taking out the --no-deps you just
> added),
>
> I get one wheel for mako: Mako-0.7.3-py33-none-any.whl
>
> I'm not seeing how this could build wheels for all the dependencies?
> where is that logic?
> I can certainly be
> cool, but you mean "including dependencies", because "pip freeze" is
flat, and
> already exhausts the dependencies, right?
>> > what does "wheeler.py pyramid" do? just pyramid itself or everything?
>>
>> Currently it would do everything (once I fix the naming bug that's
>> there), but
>>
>
> whe
> > cool, but you mean "including dependencies", because "pip freeze" is
> flat, and
> already exhausts the dependencies, right?
> > what does "wheeler.py pyramid" do? just pyramid itself or everything?
>
> Currently it would do everything (once I fix the naming bug that's there),
> but
>
when I r
On Tue, Feb 19, 2013 at 2:39 PM, Chris Withers wrote:
> Dunno what I'm doing wrong then, see the eggs being used here:
> http://jenkins.simplistix.co.uk/job/checker-buildout/86/PYTHON=2.7,label=linux/console
Weird, sounds like both the 1.3.2 and 2.0.0a3 egg recipe versions are
being fetched:
$ b
Wheel is only defined for 1 dist per archive.
On Feb 19, 2013 6:57 PM, "Vinay Sajip" wrote:
> Daniel Holth gmail.com> writes:
>
>
> > Wheel carefully preserves the meaningless purelib - platlib distinction
> even
> > though they are the same path. If you have a mixed archive you should use
> > p
Daniel Holth gmail.com> writes:
> Wheel carefully preserves the meaningless purelib - platlib distinction even
> though they are the same path. If you have a mixed archive you should use
> platlib.
>
> It is legal but inadvisable to have both! The other one would go into
> .data/platlib or .dat
On Tue, Feb 19, 2013 at 6:34 PM, Vinay Sajip wrote:
> Vinay Sajip yahoo.co.uk> writes:
>
>
> > Currently it would do everything (once I fix the naming bug that's
> there), but
> > you can basically control it by what arguments get passed to pip.
>
> Hmmm - looking at it further, I think there mig
Vinay Sajip yahoo.co.uk> writes:
> Currently it would do everything (once I fix the naming bug that's there), but
> you can basically control it by what arguments get passed to pip.
Hmmm - looking at it further, I think there might be problems with simplistic
handling of dependencies in wheele
Marcus Smith gmail.com> writes:
> cool, but you mean "including dependencies", because "pip freeze" is flat, and
already exhausts the dependencies, right?
> what does "wheeler.py pyramid" do? just pyramid itself or everything?
Currently it would do everything (once I fix the naming bug that's th
> Will build one Wheel for each requirement, including dependencies :-)
>
>
cool, but you mean "including dependencies", because "pip freeze" is flat,
and already exhausts the dependencies, right?
what does "wheeler.py pyramid" do? just pyramid itself or everything?
Marcus
On 19/02/2013 22:34, Philippe Ombredanne wrote:
On Tue, Feb 19, 2013 at 2:19 PM, Chris Withers wrote:
Am I the only one who has buildouts ending up using 2.0.1 when using:
http://downloads.buildout.org/1/bootstrap.py
...which I thought would keep zc.recipe.egg and zc.buildout pinned pre 2.0?
Vinay Sajip yahoo.co.uk> writes:
>
> Marcus Smith gmail.com> writes:
>
>> oh, I see, it works against a current installation. cool.
>> so you could convert your pip freeze output into a set of args for this
>> script.
>
> Right:
>
> pip freeze | xargs python wheeler.py
>
> Will build one Wh
On Tue, Feb 19, 2013 at 2:19 PM, Chris Withers wrote:
> Am I the only one who has buildouts ending up using 2.0.1 when using:
> http://downloads.buildout.org/1/bootstrap.py
> ...which I thought would keep zc.recipe.egg and zc.buildout pinned pre 2.0?
With this buildout.cfg:
[buildout]
parts= eggo
Marcus Smith gmail.com> writes:
> oh, I see, it works against a current installation. cool.
> so you could convert your pip freeze output into a set of args for this
> script.
Right:
pip freeze | xargs python wheeler.py
Will build one Wheel for each requirement, including dependencies :-)
Re
Hi All,
Am I the only one who has buildouts ending up using 2.0.1 when using:
http://downloads.buildout.org/1/bootstrap.py
...which I thought would keep zc.recipe.egg and zc.buildout pinned pre 2.0?
cheers,
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
On Tue, Feb 19, 2013 at 9:20 AM, Eric V. Smith wrote:
> 2. Does the metadata need to contain information about namespace
> packages? It's settable in distribute/setuptools' setup.py. I'm not sure
> if the need for it has been obviated by PEP 420 or not.
I don't think distutils or any of its exten
correction: "current installation" -> "a newly generated installation
with special options"
On Tue, Feb 19, 2013 at 12:51 PM, Marcus Smith wrote:
> Marcus
>
>> P.S. I see your script takes multiple arguments, but does it process
>> dependencies?
>>
>>
> oh, I see, it works against a current in
Marcus
> P.S. I see your script takes multiple arguments, but does it process
> dependencies?
>
>
oh, I see, it works against a current installation. cool.
so you could convert your pip freeze output into a set of args for this
script.
___
Distutils-SIG
> Although some work has been done to add wheel support to pip, you don't
> need
> this to build wheels for existing PyPI distributions if you use distlib.
> The
> following script, wheeler.py, shows how you can use an unpatched, vanilla
> pip
> to build wheels:
>
>
to be clear, the pip fork's main
On 19 February 2013 20:16, Vinay Sajip wrote:
> Following the acceptance of PEP 427 (The Wheel Binary Package Format 1.0),
> I've
> added support for Wheel to distlib [1].
Wow! I'm impressed :-)
I'll try to get some time to exercise this in the near future.
Paul.
___
Following the acceptance of PEP 427 (The Wheel Binary Package Format 1.0), I've
added support for Wheel to distlib [1].
There are still some issues cropping up in my Windows and OS X tests - the test
code uses pip to install some test distributions to build wheels from, and the
issues appear to be
Eric V. Smith trueblade.com> writes:
> Speaking of namespace packages, 2 points:
>
> 1. When deleting, you must either be aware of namespace packages and/or
> make sure to not delete source or .py[co] files that you did not
> install. One distribution could install foo.bar, and another then
> in
On 02/19/2013 05:18 AM, Vinay Sajip wrote:
> I've implemented it now in distlib, and it seems to
> work as far as it goes (no consideration has been given to namespace packages
> yet).
Speaking of namespace packages, 2 points:
1. When deleting, you must either be aware of namespace packages and/
Daniel Holth gmail.com> writes:
> If you want eby-style uninstall to be fast, index record in sqlite in a
> post-install hook.
I'm not sure what you mean by Eby-style uninstall, but uninstalling is already
fast enough, AFAIK.
> I'm horrified that "overwrite any file on my system" is a feature.
25 matches
Mail list logo
