On Monday, December 18, 2017 at 1:06:09 PM UTC, Erik Bray wrote: > > That sounds a bit bogus to me. I've never used PyCharm before and don't > know how it works, but I suspect it could be made to work with Cygwin's > Python. >
PyCharm is a closed-source product that has a wizard to pick up "the Python", and this wizard won't work with Cygwin's Python, as the product's vendor says. Bogus or not... > It's pretty low-priority for me though. I don't see how using PyCharm to > edit sage source code would be useful--it won't even do syntax highlighting > properly, unless I'm missing something. > > On Saturday, December 16, 2017 at 2:01:08 PM UTC+1, Dima Pasechnik wrote: >> >> I've already expalined here >> https://github.com/sagemath/sage-windows/issues/12 that PyCharm doesn't >> support Cygwin Python, >> and thus it's not going to be trivial to fix. The reason that we must use >> Cygwin Python is that a number of essential Sage components (i.e. Python >> extensions you need) e.g. GAP, won't work natively on Windows, as they use >> fork() and other Unix/Posix specific system functions. >> >> On Saturday, December 16, 2017 at 12:19:56 PM UTC, PHPirate wrote: >>> >>> Thanks, it sounds reasonable. But do you mean the Jupyter notebook >>> included with Sage, which you can start with >>> sage --notebook ipython >>> from the Sage shell? I do not like notebooks such as this one and >>> Mathematica because they do not go well with a VCS. Is it then possible to >>> use this Jupyter to edit and run Sage files saved in a better way, like >>> python files? >>> >> -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
