Re: [Distutils] wheel including files it shouldn't
If you'd like to have more control over what's installed, we could re-visit the idea of adding more categories of files within distributions based on the model of "copy each category of files to a [configurable] target directory". Perhaps there could even be a "necessary" flag on each category to indicate whether the code accessed those files at runtime or not. On Thu, Apr 28, 2016 at 2:31 PM Alex Grönholmwrote: > To what end? > > > 28.04.2016, 21:21, Barry Warsaw kirjoitti: > > On Apr 27, 2016, at 10:00 PM, Alex Grönholm wrote: > > > The sdist should include all the source files, including tests and > documentation. In binary distributions, however, they are just dead > weight. Do you want the full documentation and test suites to be installed > for every single dependency when you deploy your application? I sure don't. > > > Shouldn't that be left to the package author to decide? > > -Barry > > > > ___ > Distutils-SIG maillist - > Distutils-SIG@python.orghttps://mail.python.org/mailman/listinfo/distutils-sig > > > ___ > 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
Re: [Distutils] wheel including files it shouldn't
To what end? 28.04.2016, 21:21, Barry Warsaw kirjoitti: On Apr 27, 2016, at 10:00 PM, Alex Grönholm wrote: The sdist should include all the source files, including tests and documentation. In binary distributions, however, they are just dead weight. Do you want the full documentation and test suites to be installed for every single dependency when you deploy your application? I sure don't. Shouldn't that be left to the package author to decide? -Barry ___ 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
Re: [Distutils] wheel including files it shouldn't
On Apr 27, 2016, at 10:00 PM, Alex Grönholm wrote: >The sdist should include all the source files, including tests and >documentation. In binary distributions, however, they are just dead >weight. Do you want the full documentation and test suites to be installed >for every single dependency when you deploy your application? I sure don't. Shouldn't that be left to the package author to decide? -Barry pgpYtPzVV03fY.pgp Description: OpenPGP digital signature ___ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] wheel including files it shouldn't
Wheel has a proposal for a "wheel pack" command that might help you. On Thu, Apr 28, 2016, 12:46 Steve Dowerwrote: > On 27Apr2016 1445, Paul Moore wrote: > > Personally, I agree with Donald that the "normal" process of building > > a distribution should be: > > > > 1. Build the sdist. > > 2. Build wheels *from* that sdist. > > 3. Check the built sdist and wheels. > > 4. Upload the files once you've confirmed they are OK. > > > > The tools should make that as transparent as possible (I'm not averse > > to a command that builds sdist and wheels together, but such a command > > could easily use the sdist to build the wheels "behind the scenes") > > and there may be special cases (incremental builds of wheels when a > > full recompile is a significant cost) but those are quality of > > implementation details. > > One extra task that I often need is the ability to separate bdist_ext > from bdist_wheel, so that I can apply modifications to built modules > (e.g. code signing) before packaging up the wheel. > > There's probably a way to insert this step using a setuptools extension > or a setup.py hack, but it's actually most convenient to have two > completely separate commands (or options) for building and packaging. > > Cheers, > Steve > ___ > 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
Re: [Distutils] wheel including files it shouldn't
On 27Apr2016 1445, Paul Moore wrote: Personally, I agree with Donald that the "normal" process of building a distribution should be: 1. Build the sdist. 2. Build wheels *from* that sdist. 3. Check the built sdist and wheels. 4. Upload the files once you've confirmed they are OK. The tools should make that as transparent as possible (I'm not averse to a command that builds sdist and wheels together, but such a command could easily use the sdist to build the wheels "behind the scenes") and there may be special cases (incremental builds of wheels when a full recompile is a significant cost) but those are quality of implementation details. One extra task that I often need is the ability to separate bdist_ext from bdist_wheel, so that I can apply modifications to built modules (e.g. code signing) before packaging up the wheel. There's probably a way to insert this step using a setuptools extension or a setup.py hack, but it's actually most convenient to have two completely separate commands (or options) for building and packaging. Cheers, Steve ___ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
[Distutils] Use of direct references in requirements for setuptools
Hi, Currently, pip supports use of direct references[1][2] in requirement files, which means it includes code that will deal with downloading files over HTTP, or git, etc. setuptools does not have this support, and in order for setuptools to completely implement PEP 508 support, we should come up with a plan what to do when setuptools encounters a requirement that uses a direct reference. The options that I can see are: 1) When egg_info is run, exit with an error saying "Please don't do that" 2) Warn about the requirement, and that we will just depend on it, but drop the direct reference. 3) Add support to setuptools. Personally, I don't like this plan, but perhaps it's easy. 1: For example: testtools@ https://github.com/testing-cabal/testtools 2: It doesn't yet support the format specified by PEP 508, but the functionality exists and works. -- Steve Oh, in case you got covered in that Repulsion Gel, here's some advice the lab boys gave me: [paper rustling] DO NOT get covered in the Repulsion Gel. - Cave Johnson, CEO of Aperture Science ___ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] wheel including files it shouldn't
Actually, another thing you can do with the wheels at this point is to take them for a spin :-) Have pip in another virtualenv install it by using --find-links, or even setting your own local index. If you have tests embedded in your wheel, now would be a good time to run them. Best regards, Leo On 28 April 2016 at 05:03, Paul Moorewrote: > On 28 April 2016 at 00:57, Ethan Furman wrote: > > What types of things should I be doing for (3) ? > > You could check the contents of the wheels to ensure they don't > contain unexpected files :-) > > But in all honesty, probably not much. I only noted it as it's the > only place you can verify the actual files you're uploading. > Paul > ___ > 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
Re: [Distutils] wheel including files it shouldn't
On 28 April 2016 at 00:57, Ethan Furmanwrote: > What types of things should I be doing for (3) ? You could check the contents of the wheels to ensure they don't contain unexpected files :-) But in all honesty, probably not much. I only noted it as it's the only place you can verify the actual files you're uploading. Paul ___ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig