On Mon, Oct 27, 2014 at 16:45 -0400, Daniel Holth wrote:
I liked it because I agree with the TOML author that the YAML spec
gives rage; YAML seems to be defined as a bunch of things that the end
user is supposed to think are intuitive, but try understanding and
correctly parsing the full set
On Tue, 28 Oct 2014 13:15:09 +
Paul Moore p.f.mo...@gmail.com wrote:
On 28 October 2014 12:57, Antoine Pitrou solip...@pitrou.net wrote:
I would like to tell bdist_wheel to therefore tag the package as a
Python-independent, platform-dependent binary package. There doesn't
seem to be a
On Tue, 28 Oct 2014 13:15:09 +
Paul Moore p.f.mo...@gmail.com wrote:
On 28 October 2014 12:57, Antoine Pitrou solip...@pitrou.net wrote:
I would like to tell bdist_wheel to therefore tag the package as a
Python-independent, platform-dependent binary package. There doesn't
seem to be a
2014-10-28 14:20 GMT+01:00 Antoine Pitrou solip...@pitrou.net:
If I rename the file manually, is there an easy (CLI-based) way of
uploading it to PyPI?
I had the same issue for a tool that collects wheels generated by
various CI platforms to prepare a binary release.
On 28 October 2014 13:20, Antoine Pitrou solip...@pitrou.net wrote:
If I rename the file manually, is there an easy (CLI-based) way of
uploading it to PyPI?
I think twine can do that for you (and is generally recommended these
days over setup.py upload, as it uses https).
Also, there's a
Hi there,
Following up on
https://bitbucket.org/pypa/wheel/issue/124/glibc-incompatibility.
How should we deal with incompatibility of dynamically linked libraries?
Doing pip wheel numpy on a Linux 64bit machine results in , which is
linked dynamically against the GLIBC version installed on the
There's also AXON (It tries to combine the best of JSON, XML and
YAML.) – http://intellimath.bitbucket.org/axon/
___
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
On Tue, 28 Oct 2014 13:39:32 +
Paul Moore p.f.mo...@gmail.com wrote:
On 28 October 2014 13:20, Antoine Pitrou solip...@pitrou.net wrote:
If I rename the file manually, is there an easy (CLI-based) way of
uploading it to PyPI?
I think twine can do that for you (and is generally
On Oct 28, 2014, at 9:43 AM, Antoine Pitrou solip...@pitrou.net wrote:
I think twine can do that for you (and is generally recommended these
days over setup.py upload, as it uses https).
setup.py upload also uses https these days, AFAIK.
Paul forgot an important word there, *verified*
Hello,
I guess I am doing something wrong, but what?
(I took linux_x86_64 after PEP 427 and 425)
$ twine upload dist/llvmlite-0.1-py2.py3-none-linux_x86_64.whl
Uploading distributions to https://pypi.python.org/pypi
Uploading llvmlite-0.1-py2.py3-none-linux_x86_64.whl
Traceback (most recent
On 28 October 2014 10:13, Matthias Hafner hafne...@gmail.com wrote:
(in reverse order, easiest to hardest :-))
Why does that work on MacOS, btw? Are all library versions fixed there for
one version of OSX?
I believe (I'm not 100% sure as I'm a Windows user not an OSX user)
that PyPI only
On Tue, 28 Oct 2014 10:04:17 -0400
Donald Stufft don...@stufft.io wrote:
On Oct 28, 2014, at 9:43 AM, Antoine Pitrou solip...@pitrou.net wrote:
I think twine can do that for you (and is generally recommended these
days over setup.py upload, as it uses https).
setup.py upload also
On 28 October 2014 14:04, Antoine Pitrou solip...@pitrou.net wrote:
I guess I am doing something wrong, but what?
(I took linux_x86_64 after PEP 427 and 425)
Oops, I mentioned this in another thread but forgot it when responding
to you. Sorry.
PyPI does not currently allow uploading binary
Paul forgot an important word there, *verified* HTTPS.
Paul always forgets the important details when discussing security :-) Sorry.
Paul.
___
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
Hello,
Ok, so until I find a better solution I've tried hosting a wheel on a
personal server, but then I get the following error when installing it:
$ pyvenv-3.4 t
$ source t/bin/activate
(t) $ pip install
https://ssl.pitrou.net/llvmlite-0.1-py2.py3-none-linux_x86_64.whl
On Tue, Oct 28, 2014 at 2:59 AM, holger krekel hol...@merlinux.eu wrote:
On Mon, Oct 27, 2014 at 16:45 -0400, Daniel Holth wrote:
I liked it because I agree with the TOML author that the YAML spec
gives rage; YAML seems to be defined as a bunch of things that the end
user is supposed to think
Can you see what the following says (results here are from my Windows
Python 3.4 system)?
from wheel.pep425tags import get_supported
['-'.join(t) for t in get_supported()]
['cp34-none-win_amd64', 'cp34-none-any', 'cp3-none-any',
'cp33-none-any', 'cp32-none-any', 'cp31-none-any',
On Tue, 28 Oct 2014 14:44:22 +
Paul Moore p.f.mo...@gmail.com wrote:
Can you see what the following says (results here are from my Windows
Python 3.4 system)?
from wheel.pep425tags import get_supported
['-'.join(t) for t in get_supported()]
['cp34-none-win_amd64', 'cp34-none-any',
On Tue, Oct 28, 2014 at 7:04 AM, Antoine Pitrou solip...@pitrou.net wrote:
Hello,
I guess I am doing something wrong, but what?
(I took linux_x86_64 after PEP 427 and 425)
$ twine upload dist/llvmlite-0.1-py2.py3-none-linux_x86_64.whl
Uploading distributions to
On Tue, Oct 28, 2014 at 10:13 AM, Matthias Hafner hafne...@gmail.com
wrote:
Hi there,
Following up on
https://bitbucket.org/pypa/wheel/issue/124/glibc-incompatibility.
How should we deal with incompatibility of dynamically linked libraries?
Doing pip wheel numpy on a Linux 64bit machine
On 28 October 2014 14:51, Antoine Pitrou solip...@pitrou.net wrote:
Does matching really happen that way?
Unfortunately yes :-(
get_supported() introspects the system you're installing on and builds
a list of tag combinations it's willing to accept. In doing so it
misses some that I'd consider
On Tue, Oct 28, 2014 at 07:43 -0700, Chris Jerdonek wrote:
On Tue, Oct 28, 2014 at 2:59 AM, holger krekel hol...@merlinux.eu wrote:
On Mon, Oct 27, 2014 at 16:45 -0400, Daniel Holth wrote:
I liked it because I agree with the TOML author that the YAML spec
gives rage; YAML seems to be
On Tue, 28 Oct 2014 15:03:23 +
Paul Moore p.f.mo...@gmail.com wrote:
On 28 October 2014 14:51, Antoine Pitrou solip...@pitrou.net wrote:
Does matching really happen that way?
Unfortunately yes :-(
get_supported() introspects the system you're installing on and builds
a list of tag
2014-10-28 15:04 GMT+01:00 Paul Moore p.f.mo...@gmail.com:
On 28 October 2014 10:13, Matthias Hafner hafne...@gmail.com wrote:
(in reverse order, easiest to hardest :-))
Why does that work on MacOS, btw? Are all library versions fixed there for
one version of OSX?
I believe (I'm not 100%
Here is a test matrix that checks binary compatibility of OSX wheels
for many projects of the SciPy stack:
https://github.com/MacPython/scipy-stack-osx-testing
--
Olivier
___
Distutils-SIG maillist - Distutils-SIG@python.org
2014-10-28 16:22 GMT+01:00 Olivier Grisel olivier.gri...@ensta.org:
Here is a test matrix that checks binary compatibility of OSX wheels
for many projects of the SciPy stack:
https://github.com/MacPython/scipy-stack-osx-testing
And here are the results:
On 28 October 2014 15:15, Antoine Pitrou solip...@pitrou.net wrote:
Apparently already reported to pip :-)
https://github.com/pypa/pip/issues/1870
I *knew* I'd seen it somewhere. Thanks for locating it.
Reported to wheel at
On 28.10.2014 11:13, Matthias Hafner wrote:
Hi there,
Following up on
https://bitbucket.org/pypa/wheel/issue/124/glibc-incompatibility.
How should we deal with incompatibility of dynamically linked libraries?
Doing pip wheel numpy on a Linux 64bit machine results in , which is
linked
On 10/27/2014 08:26 AM, Paul Moore wrote:
On 27 October 2014 15:07, Ethan Furman et...@stoneleaf.us wrote:
Paul Moore also declaimed:
Alternatively, you could distribute all 3 files [...]
The problem I have with this method is that the last time I tried it
setup.py attempted to pre-compile
On Oct 28, 2014, at 2:20 PM, Ethan Furman et...@stoneleaf.us wrote:
On 10/27/2014 08:26 AM, Paul Moore wrote:
On 27 October 2014 15:07, Ethan Furman et...@stoneleaf.us wrote:
Paul Moore also declaimed:
Alternatively, you could distribute all 3 files [...]
The problem I have with this
In article
cafve7k4u7l4+8n3u72eher4fa8m-fcanv0q75bhm1aalfma...@mail.gmail.com,
Olivier Grisel olivier.gri...@ensta.org wrote:
Homebrew-installed Python and the system Python that comes by default
on OSX are binary compatible with wheels generated with Python from
the official OSX installer
On Mon, Oct 27, 2014 at 8:30 AM, Marius Gedminas mar...@pov.lt wrote:
Many setup.py files fail if you run them when your working directory is
not the one where the setup.py resides itself. I think you can safely
rely on that implementation detail.
agreed, but if you really wanted to be sure
32 matches
Mail list logo
