Dear Nicolas and all, On Tuesday, May 3, 2016 at 7:59:05 AM UTC-7, Nicolas M. Thiéry wrote: > > > Tangentially to the recent discussion about modularity of the Sage > library and support for packages on top of Sage, I have started > writing some notes about the different workflows that have been used > to develop and share code, either "on top of Sage", or "to be > integrated in Sage": > > https://wiki.sagemath.org/CodeSharingWorkflow > > This is rather preliminary and biased from my experience with > Sage-Combinat, and lacks many of the points that have been discussed > (e.g. the idea of affiliated packages). Please hack in and complement > with your vision! > > With only 4 years of delay, I have added a brief section on the use of native namespace packages (PEP 420) on that page. The removal of Python 2 support finally allows us to use this mechanism, which can be a robust alternative to monkey-patching.
Also, in https://trac.sagemath.org/ticket/29705 (Meta-ticket: Modularize sagelib into separate distutils packages) I describe a plan for modularizing sagelib itself, using native namespace packages. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/621b3b29-c753-4602-bd83-b1e05722bb6c%40googlegroups.com.
