On Sun, May 31, 2020 at 1:59 PM Eric Gourgoulhon <egourgoul...@gmail.com> wrote: > > Hi Tobias, > > Le dimanche 31 mai 2020 14:49:46 UTC+2, Tobias Diez a écrit : >> >> >> For now I came up with the following workaround, which works but feels like >> a huge hack: Create a file `/src/sage/test.py` with the following content. >> You can then run this file using the local python (e.g. >> ./local/bin/python3). Once you change the content of the package under >> consideration (here manifolds), rerun the "Reload manifold packages..." >> block, which reloads the files so that the changes take effect. This takes >> about one second in contrast to the 5 min of `sage -b`. > > > I'm surprised about this: usually, when I modify some source file in > src/sage/manifolds and I run sage -b afterwards, it takes only about 1 second > to rebuild Sage. > indeed, if you only touch a *.py file, it will be copied and byte-compiled by ./sage -b, but this would be the only work done by ./sage -b
if you see more, it could either be that your setup touches a lot of files, or you did actually touch *.pyx files yourself - and they take more time to rebuild. > Eric. > > -- > 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/b7b265b0-a3c4-48f4-9343-778c3504d424%40googlegroups.com. -- 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/CAAWYfq1h57TkuvkPzSCr8DT34tbq%3DM%2Bfx4Cj30VXdjavrXrp%2Bw%40mail.gmail.com.
