[Moose-dev] Building package cache

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[Moose-dev] Building package cache

Alexandre Bergel
I do not have a solution, but this is really annoying. In addition to  
the time taken by loading Moose, it makes 10 minutes just to check  
what are are dependencies Mondrian has.

Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.





_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Building package cache

Simon Denier-3

On 26 janv. 2010, at 21:07, Alexandre Bergel wrote:

I do not have a solution, but this is really annoying. In addition to the time taken by loading Moose, it makes 10 minutes just to check what are are dependencies Mondrian has.


Well, temporary solutions sometimes become less than temporary... I fear this is the case.

Maybe we can do something with an incremental, on-demand cache: whenever a class or method is imported, we check whether the cache has been built for it - if not, we built it.

--
 Simon




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev