It seems to work, I merged the change in the master of
python-appveyor-demo. Thanks!
--
Olivier
___
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
2014-09-24 23:52 GMT+02:00 Paul Moore p.f.mo...@gmail.com:
On 24 September 2014 03:45, Jonathan J. Helmus jjhel...@gmail.com wrote:
Some of us from the Scientific Python side of development have been
using appveyor to build Windows wheels for a few projects. A demo from one
of developers of
2014-09-25 0:09 GMT+02:00 Paul Moore p.f.mo...@gmail.com:
On 24 September 2014 22:58, Olivier Grisel olivier.gri...@ensta.org wrote:
Under which path?
It's now documented in
http://www.appveyor.com/docs/installed-software, but C:\PythonXY and
C:\PythonXY-x64.
Nice, thanks: I will try it now
Thank you very Steve for pushing that installer out, this is very appreciated.
What is the story for project maintainers who want to also support
Python 3.3+ (for 32 bit and 64 bit python) for their project with
binary wheels for windows? At the moment it's possible to use the
Windows SDK as
2014-09-30 18:07 GMT+02:00 Steve Dower steve.do...@microsoft.com:
Paul Moore wrote:
On 30 September 2014 16:56, Olivier Grisel olivier.gri...@ensta.org wrote:
What is the story for project maintainers who want to also support
Python 3.3+ (for 32 bit and 64 bit python) for their project
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.
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:
https://travis-ci.org/MacPython/scipy
Since PEP 440 was formally accepted in August 2014, would it make
sense to add a change log to document the amendment of the PEP, for
instance in the appendix (maybe with a link to the diff in hg)?
--
Olivier
___
Distutils-SIG maillist -
+1 overall to Nick' suggestions.
--
Olivier
___
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
Which specific room are you in? The board says 512dh.
--
Olivier
___
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
512f
--
Olivier
___
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
Congrats on the release, wheel caching for sdist is a great new feature!
--
Olivier
___
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
2015-08-12 20:51 GMT-04:00 Nathaniel Smith n...@pobox.com:
I'm a bit surprised to hear that such a PEP is needed. We (= numpy devs)
have actively been making plans to ship a BLAS wheel on windows, and AFAICT
this is totally doable now -- the blocker is windows toolchain issues, not
2015-07-17 18:50 GMT+02:00 Marcus Smith qwc...@gmail.com:
I think Linux wheel support is almost useless unless the pypa stack
provides _something_ to handle non-python dependencies.
I wouldn't say useless, but I tend to agree with this sentiment.
I'm thinking the only way to really
Test if the provided system C/C++ compiler supports OpenMP and do not use
the openmp compiler flag to fallback to a sequential build if not.
--
Olivier Grisel
___
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman
I just checked and indeed the python exec installed by miniconda does
not work on Alpine linux (launch via docker from the gliderlabs/alpine
image):
# ldd /root/miniconda3/pkgs/python-3.4.3-0/bin/python3.4
/lib64/ld-linux-x86-64.so.2 (0x7f26bd5fe000)
libpython3.4m.so.1.0 =
You can use the wheel package format to generate platform specific
packages for Windows. Have a look at the python packaging
documentation:
https://packaging.python.org
In particular:
https://packaging.python.org/en/latest/distributing.html#wheels
--
Olivier
2016-01-26 11:41 GMT+01:00 Olivier Grisel <olivier.gri...@ensta.org>:
> Maybe we could devise some syntax for /etc/python/compatibility.conf
> to state that the manylinux1 entry is only valid for Python
> interpreters such as distutils.util.get_platform() == 'linux-x86_64'?
Actu
Maybe we could devise some syntax for /etc/python/compatibility.conf
to state that the manylinux1 entry is only valid for Python
interpreters such as distutils.util.get_platform() == 'linux-x86_64'?
--
Olivier
http://twitter.com/ogrisel - http://github.com/ogrisel
2016-01-22 3:47 GMT+01:00 Chris Barker - NOAA Federal :
>
> Maybe the community will spring forth and do that -- I'm skeptical because I
> tried to to that for years for OS-X and it was just too much to do. And the
> infrastructure was there.
>
> Before pip and wheel there
Strong +1 for all Donald's proposals.
--
Olivier
___
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
> I would say there's value in having two official manylinux flavors at
once, for example manylinux2010 for maximum compatibility (it's already 8
years old as far as requirements go!) and manylinux2016 for recent systems
compatibility. Later, manylinux2022 gets released as the "recent systems
24 matches
Mail list logo