On 25/07/2016 15:30, Daniel Holth wrote:
1. There is a tool called twine that is the best way to upload to pypi
thanks I'll check that out.
2. I'm not aware of any aggregate limits but I'm pretty sure each
individual file can only be so big
In our private readonly pypi we have 93 releases. I don't think that burden
should fall on pypi. However, it's not clear to me if I should push micro
releases to pypi and then remove them when another release is made. Is there a
way to remove a 'release' completely? The edit pages seem to suggest so, but
does that remove the files?
3. Maybe the platform returns as manylinux1? Set an environment variable to
ask for static linking, and check for it in your build script?
.......
I did try manylinux1 (after PEP 513), but it didn't seem to work; looked at sys
platform, os name and the platform module, but see only this
> platform=Linux-3.16.0-50-generic-x86_64-with-redhat-5.11-Final
> sys.platform=linux2
> os.name=posix
however, it's easy enough to export an environment variable in the docker
startup script.
I did try to reduce my manylinux sizes by using a library of shared object codes
(ie a .a built from the PIC compile objs), but I didn't seem able to make this
work properly; the resulting .so seems to contain the whole library (freetype).
The windows linker seems able to pick up only the required bits so the windows
wheels are much smaller.
--
Robin Becker
_______________________________________________
Distutils-SIG maillist - [email protected]
https://mail.python.org/mailman/listinfo/distutils-sig
