On Mon, Dec 18, 2017 at 5:37 PM, PHPirate <hollandpira...@gmail.com> wrote: > Hm, it is at least worth a try (just saw your message on GH) Okay I can > understand if Sage has no syntax highlighting in any IDE on Windows, but as > the situation is now for me, is that there is no IDE in which you can type > Sage and then hit 'run' and then get Sage output. Now I think I could write > Sage in Notepad and then execute a Sage file via the Sage shell but I'm > looking to shortcut that a bit (my expectations are quite lower now I know > that Sage doesn't have a standard editor which everyone uses). > > But is it a bad idea to write Sage scripts? Did I misunderstand something, > and should I use the console only?
It's not at all a bad idea; it's just that if you want correct syntax highlighting for it you'll have to use an editor for which there is syntax highlighting support for Sage, or add it yourself to your editor of choice. Certainly there's no reason to use notepad regardless. It's just that different editors have different means of providing syntax highlighting for new languages (where Sage's syntax is just a small superset over pure Python syntax). More importantly, the default Python interpreter also isn't going to know how to execute a Sage script, though it seems that in PyCharm it's probably possible to configure the necessary options to pre-load the Sage syntax parser and then pass it a .sage script, but I haven't tried it yet. > On Monday, December 18, 2017 at 2:06:09 PM UTC+1, 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. 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. -- 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.
