Could it be easily possible to get something inbetween? I like having the .c files there next to the file (although I have to retrain myself a bit with typing) rather than having to hunt for them in some obscure not-well-documented directory. However, I would like that when I make changes to py files, I do not reload my Sage with these (potentially broken) changes and want the current behavior. I have had to do a lot of stashing when writing tests to make sure behavior doesn't change.
Best, Travis On Wednesday, August 24, 2022 at 2:59:19 AM UTC+9 Nils Bruin wrote: > That's probably due to > > https://trac.sagemath.org/ticket/32406 'Make "./configure > --enable-editable" the default' > > among other things, sys.path now has '$SAGE_ROOT/src' in it. That explains > why the "so" files are there, and the .c files are probably a consequence > of how cython compiles under those conditions. > > On Tuesday, 23 August 2022 at 10:43:53 UTC-7 Thierry > (sage-googlesucks@xxx) wrote: > >> Hi, >> >> i recently found that the src/sage directory was cluttered with some .c >> and some .so files, and that the build artifacts were back in the src/ >> directory. What is the rationale behind this move ? >> >> Ciao, >> Thierry >> >> -- 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/d97b71e9-9b5a-4601-a646-d7f53266032an%40googlegroups.com.
