When I played around with imports a while back I came away with the
impression that almost all of sage is imported rather early on in sage.all.
Without flattening out the import dependencies you won't make importing
modules much faster IMHO.
On Friday, April 4, 2014 3:23:31 PM UTC+1, R. Andrew
On Fri, Apr 4, 2014 at 3:27 AM, Volker Braun wrote:
> On Friday, April 4, 2014 1:55:40 AM UTC+1, R. Andrew Ohana wrote:
>>
>> I'm a bit confused at what you are saying. I agree that the act of
>> cleaning up the imports is essentially impossible right now due to the
>> combinatorial explosion, bu
On Friday, April 4, 2014 1:55:40 AM UTC+1, R. Andrew Ohana wrote:
>
> I'm a bit confused at what you are saying. I agree that the act of
> cleaning up the imports is essentially impossible right now due to the
> combinatorial explosion, but unless I'm missing something, we could track
> the modu
On Thu, Apr 3, 2014 at 3:49 PM, Volker Braun wrote:
>
> Simplifying the import process would definitely be nice. We should have
> some mechanism enforce a somewhat linear order, e.g. by introducing
> barriers where you are only allowed to (module-level) import stuff that
> finished importing befo
Simplifying the import process would definitely be nice. We should have
some mechanism enforce a somewhat linear order, e.g. by introducing
barriers where you are only allowed to (module-level) import stuff that
finished importing before the previous barrier. Perhaps ideally a linear
order wher
