I'm trying out to submit a wheel to testpypi.python.org and then
install it from there with pip. It doesn't work; what does the
following error message mean?
c:\>py -3.4 -m pip install py2exe -r https://testpypi.python.org/pypi/
Exception:
Traceback (most recent call last):
File "C:\Python34-6
On 23 January 2014 08:28, Thomas Heller wrote:
> I'm trying out to submit a wheel to testpypi.python.org and then
> install it from there with pip. It doesn't work; what does the
> following error message mean?
>
> c:\>py -3.4 -m pip install py2exe -r https://testpypi.python.org/pypi/
The flag -
Am 23.01.2014 10:05, schrieb Paul Moore:
On 23 January 2014 08:28, Thomas Heller wrote:
I'm trying out to submit a wheel to testpypi.python.org and then
install it from there with pip. It doesn't work; what does the
following error message mean?
c:\>py -3.4 -m pip install py2exe -r https://te
On Thu, Jan 23, 2014 at 1:42 AM, Thomas Heller wrote:
> Am 23.01.2014 10:05, schrieb Paul Moore:
>
>> On 23 January 2014 08:28, Thomas Heller wrote:
>>>
>>> I'm trying out to submit a wheel to testpypi.python.org and then
>>> install it from there with pip. It doesn't work; what does the
>>> fol
After having used and built bdist_wininst installers for years (well, I
should say decades) I have recently started playing with pip.
In theory, it is a grat solution. Respects virtual environments
(although I haven't tested them yet), allows to freeze to a requirements
file, and so on.
It woul
On 23 January 2014 11:48, Thomas Heller wrote:
> After having used and built bdist_wininst installers for years (well, I
> should say decades) I have recently started playing with pip.
Thanks for trying this - it's really useful to have a newcomer's
perspective to the pip experience.
> However,
I've redone it so it doesn't require make, and renamed the Makefile.
However, it's quite a bit slower now. Also, "python setup.py clean"
doesn't appear to remove all the build artifacts.
Is there some way I can speed it up?
Is there some way I can automatically remove the build artifacts
without
Am 23.01.2014 13:16, schrieb Paul Moore:
On 23 January 2014 11:48, Thomas Heller wrote:
Is there a solution to this? I've seen that the wheel tool can convert
bdist_wininst installers into wheels - does this work for the packages
I mentioned above? Do we have to build or convert to wheel thos
I'm reading up and done all those peps:
425 - compaibility tags
426 - metadata 2.0
427 - wheel binary format 1.0
440 - version identification and dependency specifications
and trying to make sense from them. Well, they make sense to me,
but to what do they apply?
Example: I can now build, uplo
On Thu, Jan 23, 2014 at 12:16:02PM +, Paul Moore wrote:
>
> The official numpy installer uses some complex magic to select the
> right binaries based on your CPU, and this means that the official
> numpy "superpack" wininst files don't convert (at least I don't think
> they do, it's a while si
On Thu, Jan 23, 2014 at 9:23 AM, Thomas Heller wrote:
> I'm reading up and done all those peps:
>
> 425 - compaibility tags
> 426 - metadata 2.0
> 427 - wheel binary format 1.0
> 440 - version identification and dependency specifications
>
> and trying to make sense from them. Well, they make sen
On Thu, 23/1/14, Daniel Holth wrote:
supports_environments is not implemented.
Perhaps not in pip and wheel, but there is support in distlib and distil.
Specifically, distil should present a list of failing clauses in
supports_environments for an
>
>
> Are the specifications in the PEPs above implemented somewhere
> or are they only 'specifications'?
>
The Packaging User Guide is maintaining a summary of the relevant PEPs that
gives a brief description of the "user impact" and "implementation" (i.e.
whether projects are actually implementi
On Thu, Jan 23, 2014 at 3:42 PM, Oscar Benjamin
wrote:
> On Thu, Jan 23, 2014 at 12:16:02PM +, Paul Moore wrote:
> >
> > The official numpy installer uses some complex magic to select the
> > right binaries based on your CPU, and this means that the official
> > numpy "superpack" wininst files
On Thu, 23/1/14, Marcus Smith wrote:
> The Packaging User Guide is maintaining a summary
> of the relevant PEPs that gives a brief description of the
> "user impact" and "implementation" (i.e.
> whether projects are actually implementing any of
> this
>
>
> A lot of this stuff is implemented in distlib and distil (distlib itself
> is just a library that provides the underpinnings, and some of the
> functionality required, such as actually installing stuff, is implemented
> in distil. I assume it's OK to add references to these? For example,
> di
We need pip's build to become more like conda build.
http://docs.continuum.io/conda/build.html
A simple recipe, not necessarily part of the to-be-built package
source, invokes build.sh to create a package. In that kind of system
things like distil can be used at will.
On Thu, Jan 23, 2014 at 2:12
> certainly mention the distlib implementations,
> but also let's be clear if there is a pypa-recommend
> tool that is user-facing (like pip), that is using those
> parts of distlib.
> In most cases, that is not true currently.
> As for mentioning di
Am 23.01.2014 19:52, schrieb Ralf Gommers:
On Thu, Jan 23, 2014 at 3:42 PM, Oscar Benjamin
mailto:oscar.j.benja...@gmail.com>> wrote:
On Thu, Jan 23, 2014 at 12:16:02PM +, Paul Moore wrote:
>
> The official numpy installer uses some complex magic to select the
> right b
Are the specifications in the PEPs above implemented somewhere
or are they only 'specifications'?
The Packaging User Guide is maintaining a summary of the relevant PEPs
that gives a brief description of the "user impact" and "implementation"
(i.e. whether projects are actually implement
On 24 January 2014 06:25, Thomas Heller wrote:
> Am 23.01.2014 19:52, schrieb Ralf Gommers:
>> On Thu, Jan 23, 2014 at 3:42 PM, Oscar Benjamin
>> mailto:oscar.j.benja...@gmail.com>> wrote:
>>
>> On Thu, Jan 23, 2014 at 12:16:02PM +, Paul Moore wrote:
>> >
>> > The official numpy
On Thu, Jan 23, 2014 at 12:25 PM, Thomas Heller wrote:
> Did I say this before? I would suggest that numpy develops a way
> where all the SSE binary variations would be installed, and the
> appropriate ones be loaded at runtime, depending on the user's CPU
> capabilities. This would also allow
On 24 Jan 2014 08:03, "Chris Barker" wrote:
>
> On Thu, Jan 23, 2014 at 12:25 PM, Thomas Heller
wrote:
>>
>> Did I say this before? I would suggest that numpy develops a way
>> where all the SSE binary variations would be installed, and the
>> appropriate ones be loaded at runtime, depending on
On 23 January 2014 23:58, Nick Coghlan wrote:
>
> I really think that's our best near term workaround - still room for
> improvement, but " pip install numpy assumes SSE2" is a much better
> situation than "pip install numpy doesn't work on Windows".
Is it? Do you have any idea what proportion of
On Jan 23, 2014, at 4:17 PM, Oscar Benjamin wrote:
> On 23 January 2014 23:58, Nick Coghlan wrote:
>>
>> I really think that's our best near term workaround - still room for
>> improvement, but " pip install numpy assumes SSE2" is a much better
>> situation than "pip install numpy doesn't work
25 matches
Mail list logo
