Hi so it seems the issue is somehow resolved. From what I've researched, it could be due to one of these reasons: 1. python version incompatible 2. check the PATH variable and remove some of the questionable PATH variables per the README file. This is a wsl ubuntu on Windows specific issue. 3. the modification is buggy itself, resulting in a build failure 4. The alternative is always to use make build though with longer time
On Thursday, March 20, 2025 at 5:21:27 PM UTC-4 Henry Wu wrote: > Hi sage math communities: > I'm currently working on an issue in the sage repo, and all the changes I > made is in one pyx. file. Per my understanding of the dev workflow in the > sage documentation, > 1. If I changed only python files, I can simply restart sage to test > 2. If other files were changed (in this case, pyx file) I need to rebuild > sage via "./sage -br". > My issue is, after I successfully rebuild using "./sage -br" command, my > machine returned these lines after calling "./sage": > "Traceback (most recent call last): > File "/home/zhenyuw/sage/src/bin/sage-ipython", line 9, in <module> > from sage.misc.banner import banner > ModuleNotFoundError: No module named 'sage'" > My machine is wsl ubuntu on windows. I am confused as to what I've missed > in this process. > Also, I realize this process of "re-building" is rather time-consuming. Is > there other more efficient ways for sage dev testing? > Regards > Henry > -- You received this message because you are subscribed to the Google Groups "sage-gsoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-gsoc+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/sage-gsoc/e7eee678-422f-4a92-ad39-2b39321c2fben%40googlegroups.com.
