Log file Viewer

[05:58:28] <pombreda> omry: re

[05:58:29] <pombreda> > is it possible to have two packages in the same setup.py that uses two different MANIFEST.in files?

[05:59:13] <pombreda> not that I know of, but what you can do is have a script that calls setup.py twice replacing the manifest.in before each call

[05:59:57] <pombreda> I do that here for instance https://github.com/nexB/scancode-toolkit/blob/develop/etc/release/release.sh

[06:00:42] <pombreda> my use case is to have a "release" manifest that does not include the test scripts and data files (that are rather big... and I do not want them in the release sdist ;) )

[06:19:47] <omry> pombreda, thanks. that sounds like a pretty nasty hack :). I opted to move my second package to a sub directory, along with it's own setup.

[06:20:32] <omry> not what I wanted but it's much easier than coaxing setuptools to package the packages the way I want it to.

[06:37:17] <pombreda> omry: good. There is no setup.py --manifest=path/to/my/manifest

[06:37:26] <pombreda> which would have been the way

[06:37:41] <pombreda> but it is too exotic a use case to be part of the tool IMHO

[08:42:42] <FFY00> perfect application for a custom PEP517 backend

[13:56:21] <elibrokeit> pombreda: why do you have two sdists, exactly? What does the "non-release one" accomplish?

[13:57:25] <elibrokeit> also it appears you're including your CI *.yml configs in your sdists, why....

[13:57:34] <pombreda> elibrokeit: the regular one has everything including tests code and tests data

[13:57:48] <elibrokeit> and when and where do you upload it

[13:57:52] <pombreda> elibrokeit: and trust me that's useful:

[13:57:53] <pombreda> $ du --si -s tests/

[13:57:53] <pombreda> 190M tests/

[13:58:31] <pombreda> elibrokeit: that for moving around locally and not for upload to Pypi and general consumption

[13:59:14] <elibrokeit> curious why you don't move around locally using git

[13:59:55] <pombreda> moving around, as in playing. For instance I use that for some verification at times on a vanilla VM that has no git installed (really a vanilla OS) on windows and mac.

[14:00:24] <pombreda> (two OSses that I love to hate)

[14:03:44] <pombreda> so this is just a convenience. When you support win and mac, the warm fuzzy feelings you can have with linux distros packaging and installation dissolves quite rapidly.

[14:26:35] <elibrokeit> hmm

[14:26:49] <elibrokeit> I'd probably use git-archive in that case to transfer files

[14:28:59] <elibrokeit> it seems like a huge hack to support a weird edge case. Especially I have to wonder, why is the "real" manifest not the default one, and the special "I need to upload an sdist to my test VM without git" manifest, the one invoked by a special script?

[14:37:53] <pombreda> that's a tiny hack ... just a few lines of bash :) but this is likely going away, as we likely will drop sdist entirely to provide instead packages for Linux (and installers for win/mac) making this a non issue and the only MANIFEST needed with have everything on it

[14:39:10] <pombreda> > I'd probably use git-archive in that case to transfer files

[14:39:10] <pombreda> That's a good point.... in these case that's really a tarball of most everything except local caches, .git tmp/ and ... and ... :) which is why a MANIFEST has been handy

[14:46:35] <elibrokeit> well, git-archive doesn't store .git or anything else that isn't actually checked into git :)

[14:46:47] <elibrokeit> though you would need to git commit anything you want to archive and transfer

[15:53:08] <pombreda> elibrokeit: thanks!

[15:53:20] <pombreda> looks like a simpler thing

[21:18:02] <cooperlees> anyone who uses black formatter - I and another contributor hang out in #blackformatter