1. There is a tool called twine that is the best way to upload to pypi 2. I'm not aware of any aggregate limits but I'm pretty sure each individual file can only be so big
3. Maybe the platform returns as manylinux1? Set an environment variable to ask for static linking, and check for it in your build script? On Mon, Jul 25, 2016 at 8:05 AM Robin Becker <ro...@reportlab.com> wrote: > I have started to make manylinux wheels for reportlab. > > Our work flow is split across multiple machines. In the end we create a > total of > 19 package files (10 manylinux, 8 windows + 1 source); these total 53Mb. > > 1) Is there a convenient way to upload a new version starting from the > package > files themselves? Normally we try to test the packages before they are > uploaded > which implies we cannot just use the distutils upload command. > > > 2) I assume I cannot just keep on uploading new versions to pypi. > Presumably I > would have to delete a micro release before uploading a new one and only > keep > significant releases. > > 3) The manylinux builds are significantly larger than the windows ones > because > the manylinux build is not statically linking those bits of freetype which > we > use. Is there a way to detect that I'm building under manylinux? > -- > Robin Becker > _______________________________________________ > Distutils-SIG maillist - Distutils-SIG@python.org > https://mail.python.org/mailman/listinfo/distutils-sig >
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
