On Mon, Feb 1, 2016 at 8:06 AM, Efraim Flashner <[email protected]> wrote:
> I looked over the commit but not deeply enough yet, would it be possible to > use some of the logic in this to fix the package-with-python2 issue? Here's a potential solution for 'package-with-python2': module introspection. AIUI, the issue is that some Python 2 packages need extra manual tweaking, but 'package-with-python2' creates package variants without these tweaks. Our algorithm could look up 'python2-foo' in (gnu packages python) and use that package object, if it exists. This would stop the recursive transformation for that branch of the dependency graph and allow us to tweak Python 2 variants as needed without fear. Also, somewhat unrelated, package-with-python2 could add setuptools as an input to these packages so we can remove all the unnecessary usage of it in Python 3 packages. Thoughts? - Dave
