>I haven't tested it, ... Why is it suboptimal? I used the word "suboptimal" to reffer to the virtualbox based solution, not to the cygwin one.
If by "native" you mean "without cygwin"... i am afraid that that we would be very far away from that. Not only from the sage side (at the end of the day, most of the code writen by sage devs is portable python/cython), but from the thirthd party pieces: Singular is not natively ported to windows (runs under cygwin), GAP for windows uses cygwin too, Pari/gp also runs under cygwin (and has limitations compared to the linux version)... So the native windows port of sage is really unlikely to happen in the mid term. Considering that, Sage releases official versions that work under windows (via virtualbox), and also a cygwin port is being worked on (although it is true that, with the virtual machine available, this has become a secondary effort). And since you mention the one-click installer... that was pretty much what the GUI project that we suggested was about. As i said, no student showed interest in working on that. As i said, the statement that the sage project is turning its back on windows system is far from being true. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
