Re: [sage-devel] ./sage -br quite fast?
On 5 November 2014 23:11, William Stein wst...@gmail.com wrote: On Wed, Nov 5, 2014 at 2:47 PM, john_perry_usm john.pe...@usm.edu wrote: Thank you for the reply. What happens after you iterate the above operation? More precisely, after it does finish building, what happens if you change that Python file and again do sage -br? Your question is apt: in fact, I had a typo in the file, so Sage crashed when it tried to restart after building. I fixed the typo, and sage -br quickly incorporated the changes, which seem to work great (have to check it by hand though). Does that explain what it was? john perry It's an important data point for whoever looks into this further (not me). Another useful test to have done (too late now unless you make a fresh branch prehaps) would be to have done sage -b *before* making any changes to any files. If that did anything at all, then there was work which needed to be done at least once, and probably only once, after switching branches. John William -- William Stein Professor of Mathematics University of Washington http://wstein.org -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] ./sage -br quite fast?
Thanks. I'll try to remember that in the future. Another data point: After committing not seeing the changes on a ticket (see other post), I find that Sage has reverted to the state of the code, pre-changes. john perry On Thursday, November 6, 2014 10:27:21 AM UTC+1, John Cremona wrote: On 5 November 2014 23:11, William Stein wst...@gmail.com javascript: wrote: On Wed, Nov 5, 2014 at 2:47 PM, john_perry_usm john@usm.edu javascript: wrote: Thank you for the reply. What happens after you iterate the above operation? More precisely, after it does finish building, what happens if you change that Python file and again do sage -br? Your question is apt: in fact, I had a typo in the file, so Sage crashed when it tried to restart after building. I fixed the typo, and sage -br quickly incorporated the changes, which seem to work great (have to check it by hand though). Does that explain what it was? john perry It's an important data point for whoever looks into this further (not me). Another useful test to have done (too late now unless you make a fresh branch prehaps) would be to have done sage -b *before* making any changes to any files. If that did anything at all, then there was work which needed to be done at least once, and probably only once, after switching branches. John William -- William Stein Professor of Mathematics University of Washington http://wstein.org -- 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+...@googlegroups.com javascript:. To post to this group, send email to sage-...@googlegroups.com javascript:. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] ./sage -br quite fast?
For the sake of adding more data points: I've made several more changes, and not observed that behavior again. For some odd reason, that same typo kept popping up, unless I kept the file open, but right now everything seems fine ( I've since closed the file). Thank you again for the help :-) john perry On Thursday, November 6, 2014 12:11:59 AM UTC+1, William wrote: On Wed, Nov 5, 2014 at 2:47 PM, john_perry_usm john@usm.edu javascript: wrote: Thank you for the reply. What happens after you iterate the above operation? More precisely, after it does finish building, what happens if you change that Python file and again do sage -br? Your question is apt: in fact, I had a typo in the file, so Sage crashed when it tried to restart after building. I fixed the typo, and sage -br quickly incorporated the changes, which seem to work great (have to check it by hand though). Does that explain what it was? john perry It's an important data point for whoever looks into this further (not me). William -- William Stein Professor of Mathematics University of Washington http://wstein.org -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] ./sage -br quite fast?
Hello According to the developer's guide, the command ./sage -br should be quite fast. I just made a 2-3 line alteration to sage/rings/polynomial/multipolynomial_ideal.py and got this output: sage$ ./sage -br scons: `install' is up to date. Updating Cython code Compiling sage/algebras/quatalg/quaternion_algebra_element.pyx because it depends on ./sage/structure/element.pxd. Compiling sage/algebras/letterplace/free_algebra_letterplace.pyx because it depends on ./sage/structure/element.pxd. Compiling sage/algebras/letterplace/free_algebra_element_letterplace.pyx because it depends on ./sage/structure/element.pxd. ...and there's lots more where that came from. Looks like I'll be waiting a while, in fact. I modify a handful of lines in one Python (!) file, and the entire Cython (!) structure gets rebuilt? Did I do something wrong? This is on OSX, by the way, with Sage 6.3. I don't believe it's a binary download, but it might be. If either of those is the cause of this, I'd be grateful for explicit confirmation. thanks john perry -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] ./sage -br quite fast?
On Wed, Nov 5, 2014 at 1:41 PM, john_perry_usm john.pe...@usm.edu wrote: Hello According to the developer's guide, the command ./sage -br should be quite fast. I just made a 2-3 line alteration to sage/rings/polynomial/multipolynomial_ideal.py and got this output: sage$ ./sage -br scons: `install' is up to date. Updating Cython code Compiling sage/algebras/quatalg/quaternion_algebra_element.pyx because it depends on ./sage/structure/element.pxd. Compiling sage/algebras/letterplace/free_algebra_letterplace.pyx because it depends on ./sage/structure/element.pxd. Compiling sage/algebras/letterplace/free_algebra_element_letterplace.pyx because it depends on ./sage/structure/element.pxd. ...and there's lots more where that came from. Looks like I'll be waiting a while, in fact. I modify a handful of lines in one Python (!) file, and the entire Cython (!) structure gets rebuilt? Did I do something wrong? This is on OSX, by the way, with Sage 6.3. I don't believe it's a binary download, but it might be. If either of those is the cause of this, I'd be grateful for explicit confirmation. What happens after you iterate the above operation? More precisely, after it does finish building, what happens if you change that Python file and again do sage -br? William -- William Stein Professor of Mathematics University of Washington http://wstein.org -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] ./sage -br quite fast?
Thank you for the reply. What happens after you iterate the above operation? More precisely, after it does finish building, what happens if you change that Python file and again do sage -br? Your question is apt: in fact, I had a typo in the file, so Sage crashed when it tried to restart after building. I fixed the typo, and sage -br quickly incorporated the changes, which seem to work great (have to check it by hand though). Does that explain what it was? john perry -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] ./sage -br quite fast?
On Wed, Nov 5, 2014 at 2:47 PM, john_perry_usm john.pe...@usm.edu wrote: Thank you for the reply. What happens after you iterate the above operation? More precisely, after it does finish building, what happens if you change that Python file and again do sage -br? Your question is apt: in fact, I had a typo in the file, so Sage crashed when it tried to restart after building. I fixed the typo, and sage -br quickly incorporated the changes, which seem to work great (have to check it by hand though). Does that explain what it was? john perry It's an important data point for whoever looks into this further (not me). William -- William Stein Professor of Mathematics University of Washington http://wstein.org -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
