Re: [sage-devel] Re: New package creation - advice/help requested

2023-07-06 Thread 'Travis Scrimshaw' via sage-devel
Not so much, but because people working in matroids usually need more speed, it tends to mean more Cython code. Compare how your implementation is done with the matroids in Sage. (For instance, you can have a category (even with Cython), but there are a number of categories that are more meant

Re: [sage-devel] Re: New package creation - advice/help requested

2023-07-05 Thread Aram Dermenjian
In essence, yes we're expecting to change much of the code as the structure will be changing in addition to fixes to some major bugs in the code. Moreover, I'm working on this with two (undergraduate) interns that I have and so they're newer to programming so I wanted them to work in a more "sandbo

[sage-devel] Re: New package creation - advice/help requested

2023-07-02 Thread 'Travis Scrimshaw' via sage-devel
Hi Aram, Can you explain a bit more why you aren't just integrating it into Sage now? Are you're expecting to have major API changes? There would likely be a push to change to using more Cython, but it doesn't need to be feature complete to be a part of Sage and internal/implementation detail

[sage-devel] Re: New package creation - advice/help requested

2023-06-29 Thread Matthias Koeppe
On Thursday, June 29, 2023 at 3:01:58 AM UTC-7 Aram Dermenjian wrote: it seems the method I was using to create a new package is no longer valid. For example, when I try and do an install, I get the following error: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build an