Re: Terrible performance of Python dependency generator

2015-11-23 Thread Jeffrey Johnson
> On Nov 23, 2015, at 4:16 AM, Jacek Konieczny wrote: > > On 2015-11-22 22:03, Jeffrey Johnson wrote: >> Dependencies are automatically generated only for executable files. > > That is not true for Python dependencies and this would not work for > Python dependencies. > (aside) “Only executab

Re: Terrible performance of Python dependency generator

2015-11-23 Thread Jacek Konieczny
On 2015-11-22 22:03, Jeffrey Johnson wrote: Dependencies are automatically generated only for executable files. That is not true for Python dependencies and this would not work for Python dependencies. There are two useful types of Python dependencies: 1. python(abi) – this is extracted from

Re: Terrible performance of Python dependency generator

2015-11-23 Thread Jeffrey Johnson
> On Nov 23, 2015, at 3:54 AM, Elan Ruusamäe wrote: > > On 22.11.2015 22:39, Jacek Konieczny wrote: >> /usr/lib/rpm/pythoneggs.py is used to find the dependencies and it is >> not that slow by itself… but it is called twice (Provides + Requires) >> for each file in /usr/share/pythonX.Y. And big

Re: Terrible performance of Python dependency generator

2015-11-23 Thread Elan Ruusamäe
On 22.11.2015 22:39, Jacek Konieczny wrote: /usr/lib/rpm/pythoneggs.py is used to find the dependencies and it is not that slow by itself… but it is called twice (Provides + Requires) for each file in /usr/share/pythonX.Y. And big Python packages have lots of files there. Most of them not adding

Re: Terrible performance of Python dependency generator

2015-11-22 Thread Jeffrey Johnson
> On Nov 22, 2015, at 3:39 PM, Jacek Konieczny wrote: > > Hi, > > We will probably need to rebuild the python-* packages again and I > already hate that. Such python-django takes 45 minutes to build and most > of that is in the auto-dependency generator. That is insane! It should > not take tha