No, 13190 would not solve the problem, and it would be very difficult to have the entire list generated automatically, since setting up the appropriate flags, source files, etc would be very difficult, if not impossible to automate.
13031 would do a lot to help the situation -- the point of the ticket is to use Cython's built in logic to deal with dependency checking and generation of c files (which is finally robust enough to handle the complexity of sage). Since the patch almost rewrites module_list.py, it probably needs rebasing again (I haven't rebased since 5.4.beta1). On Tue, Oct 16, 2012 at 12:40 AM, Nicolas M. Thiery < [email protected]> wrote: > Hi! > > Having to manually update the packages list in the setup.py file > whenever one adds a new directory to the sage sources is a pain, and a > constant source of conflicts between patches. Shall we instead build > this list automatically, either at compile time or at sage's startup? > Would this by any chance be taken care of by the upcoming change to > setuptools #13190? > > Cheers, > Nicolas > -- > Nicolas M. Thiéry "Isil" <[email protected]> > http://Nicolas.Thiery.name/ > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > Visit this group at http://groups.google.com/group/sage-devel?hl=en. > > > -- Andrew -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
