[sage-devel] macports
This is the first time I've seen this: Found MacPorts in /opt/local/bin/port * Found either MacPorts or Fink in your path, which potentially wrecks the Sage build process. You should make sure MacPorts and Fink cannot be found. Either: (1) rename /opt/local and /sw, or (2) change PATH and DYLD_LIBRARY_PATH (Once Sage is built, you can restore them.) * Would it be excessively uncivilised to *automatically* change the path during the build process? david --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: macports
On Oct 5, 2008, at 02:11 , David Philp wrote: Would it be excessively uncivilised to *automatically* change the path during the build process? Well, the kind of people who will come across it will be capable of changing their own path---and maybe sensitive. And, it might require root permissions. Changing the PATH and related environment variables does not require any permissions. However, these variables can be modified each time a shell starts up, depending on how the startup works, so that may not suffice. It's kind of tricky, but David's suggestion makes sense to me. I've worked around this by changing the settings in my startup file, and that may be uncivilized. If it can be done without modifying the local startup files, that would be ideal. Any other thoughts? Justin -- Justin C. Walker, Curmudgeon-At-Large Director Institute for the Enhancement of the Director's Income Weaseling out of things is what separates us from the animals. Well, except the weasel. - Homer J Simpson --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: macports
Would it be excessively uncivilised to *automatically* change the path during the build process? Well, the kind of people who will come across it will be capable of changing their own path---and maybe sensitive. And, it might require root permissions. D --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: review request for trac #4164 (polyhedra.py)
I don't think its enough to lift by monotonically increasing values, although maybe if it increases fast enough it would work. I will take a look at this patch as soon as I can. -Marshall On Oct 4, 7:59 pm, Arnaud Bergeron [EMAIL PROTECTED] wrote: 2008/9/29 mhampton [EMAIL PROTECTED]: I thought I would explicitly point this one out because I had been reviewing #4164 (work by Arnaud Bergeron), but now I am also contributing code and I think the best scenario is to have someone else take a look. Mike Hansen has looked at polyhedra.py before, so he is a candidate if willing, but it would be great if someone else takes a look. Polyhedra.py (in sage/geometry) is still in its early stages; eventually I hope for it and other things in the geometry group to provide most of the functionality of polymake and other packages if they can't be made part of standard sage. Because the optimal design is far from clear to me, I want to encourage more eyeballs on it (I am an enthusiastic amateur when it comes to polytopes, not an expert). Marshall Hampton About this patch I have an idea for an improvement that would make it work 100% in all cases. I can't believe I didn't think of this sooner. The idea is that instead of adding a random value in the extra dimension for the lifting we can only add an monotonically increasing value. I tried this on the simple 4D example that was in doctest before as well as the monster that crashed my code (and my hopes) before and they both worked repeatedly (with a newly created polyhedron, otherwise it just hits the cache). I visualized the monster one (with ugly hacks) and the results looks correct. I haven't manually inspected every surface produced though, so there might be some errors. So I turn to you (or anybody else that wants) for examples that could break this before submitting final version no 42 to trac. Use the attached patch (requires trac_4164_merge.patch from the trac ticket) to try yourself or send me lists of vertices for polyhedron. Arnaud tentative_4164.patch 1KViewDownload --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: macports
On Oct 5, 2008, at 5:32 AM, Justin C. Walker wrote: On Oct 5, 2008, at 02:11 , David Philp wrote: Would it be excessively uncivilised to *automatically* change the path during the build process? Well, the kind of people who will come across it will be capable of changing their own path---and maybe sensitive. And, it might require root permissions. Changing the PATH and related environment variables does not require any permissions. However, these variables can be modified each time a shell starts up, depending on how the startup works, so that may not suffice. It's kind of tricky, but David's suggestion makes sense to me. I've worked around this by changing the settings in my startup file, and that may be uncivilized. If it can be done without modifying the local startup files, that would be ideal. Any other thoughts? Two other thoughts. (1) this is the first time ever that I can recall sage not building on my machine by simply issuing make. I think it's a Bad Thing that this now happens. It will happen to me every time I build sage because I do not want to remove MacPorts permanently. (2) Here's how I got around it. I looked at my environment by typing env. Then I manually typed in export PATH=, including all the directories in my original PATH minus the ones involving /opt/local. Then I ran make. This seems to work. But Justin suggests above that this might not be enough; perhaps other shells being created during the build process are using a path from some startup script, which I haven't changed. So even though I am the kind of person who is capable of changing my path, but I actually have no idea what I'm doing, and quite possibly tricked sage into doing the wrong thing anyway. david --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: macports
On Sun, Oct 5, 2008 at 6:52 AM, David Harvey [EMAIL PROTECTED] wrote: On Oct 5, 2008, at 5:32 AM, Justin C. Walker wrote: On Oct 5, 2008, at 02:11 , David Philp wrote: Would it be excessively uncivilised to *automatically* change the path during the build process? Well, the kind of people who will come across it will be capable of changing their own path---and maybe sensitive. And, it might require root permissions. Changing the PATH and related environment variables does not require any permissions. However, these variables can be modified each time a shell starts up, depending on how the startup works, so that may not suffice. It's kind of tricky, but David's suggestion makes sense to me. I've worked around this by changing the settings in my startup file, and that may be uncivilized. If it can be done without modifying the local startup files, that would be ideal. Any other thoughts? Two other thoughts. (1) this is the first time ever that I can recall sage not building on my machine by simply issuing make. I think it's a Bad Thing that this now happens. It will happen to me every time I build sage because I do not want to remove MacPorts permanently. (2) Here's how I got around it. I looked at my environment by typing env. Then I manually typed in export PATH=, including all the directories in my original PATH minus the ones involving /opt/local. Then I ran make. This seems to work. But Justin suggests above that this might not be enough; perhaps other shells being created during the build process are using a path from some startup script, which I haven't changed. So even though I am the kind of person who is capable of changing my path, but I actually have no idea what I'm doing, and quite possibly tricked sage into doing the wrong thing anyway. We could change things so that the shell script I wrote that calls spkg-install (I think it's maybe sage-spkg or something) cleans the path. Does MacPorts also modify *LD_LIBRARY_PATH*? Justin -- if we make sure no environment variables reference /opt and /sw, might that be enough to imply that nothing in macports (or fink) is going to get pulled in during the build? I am for creating a workaround like above rather than forcing the user to do something funny every time. I'm for this because at least MacPorts (and Fink) are sufficiently standard on OS X that we can figure out how to workaround them. William --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Italian translation of SAGE tutorial
I've open a new page on the SAGE wiki: http://wiki.sagemath.org/i18n/Italian Please, add your name in that page if you are interested in the project. Cristian p.s.: I hope we can use the SAGE wiki for this. Please, if it isn't so let me know and delete the page. (in any case I believe there should be some place where we can put the translations and work on them.) Thanks in advance. Ciao ciao Cristian --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Italian translation of SAGE tutorial
On Sun, Oct 5, 2008 at 12:05 PM, CristianCantoro [EMAIL PROTECTED] wrote: I've open a new page on the SAGE wiki: http://wiki.sagemath.org/i18n/Italian Please, add your name in that page if you are interested in the project. Cristian p.s.: I hope we can use the SAGE wiki for this. Please, if it isn't so let me know and delete the page. (in any case I believe there should be some place where we can put the translations and work on them.) Please definitely use the Sage wiki for this. I give you permission and endorsement! William --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
