On Wed, Feb 10, 2016 at 01:15:58PM -0500, Neal Gompa wrote: > On Wed, Feb 10, 2016 at 5:38 AM, Petr Viktorin <pvikt...@redhat.com> wrote: > > On 02/09/2016 08:26 PM, Zbigniew Jędrzejewski-Szmek wrote: > >> The scheme with automatic dependency generation could be implemented > >> gradually, by introducing the automatic provides and dependencies > >> generators, without removing current manual provides. Then when the > >> generated dependencies seem to be right, removing manual dependencies. > >> > >> Automatic dependency generation would benefit the whole ecosystem of > >> Python packages in Fedora. > > > > It would. It's also practically impossible to write such generators > > correctly. (Please prove me wrong!) > > > > It's even harder to write such generators for the stdlib than external > > libraries, because Python's built-in types assume that stdlib there. For > > example, str.encode() needs the encoding modules, and there's no import > > statement to analyze. > > > > I hope that it's not impossible to write such generators correctly. > That said, it would really help if upstream Python would change things > up a bit so that the stdlib declares what modules it provides, and > that the modules can be declared in the requires for eggs and wheels. > That would make it much easier to make generators that can account for > stdlib stuff.
I think that Python3 is much nicer here than Python2 because of absolute imports. 'import foo' is always a top level module. Zbyszek -- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
