Hello, On 16/08/16 17:48, Dima Pasechnik wrote:
On Tuesday, August 16, 2016 at 6:14:27 PM UTC+1, Simon King wrote:
>>
I made progress turning my optional old-style group cohomology spkg into a new style package (called "modres", to be added to Sage at some point) depending on another new-style package (called "meataxe", already part of Sage), both being wrapped by an OptionalExtension in the Sage library. Alert me if that's not the way to do it...
This is *one* way to do. You can also distribute your package as an independent Python module. That is to say, you can also move the "Cython interface part" to your package. One advantage of this approach is that you will not have to perform "make" to get the interface compiled. Just
$ sage -pip install my_tarball.tgz
My first question is about logging.
>> [snip]
My second question is about optional tests. It has been discussed before whether to have a way to mark *all* tests of a module optional. Has it meanwhile be implemented in the test framework? After all, we now have OptionalExtension in module_list.py, and obviously the tests of an optional extension should be optional, isn't it?
If you use the independent module approach then this does not apply. However, it comes with a new question: how do we run the testsuite of an already installed optional/experimental package? Should the patchbots be configured do that by default?
Vincent -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
