Closed #1351 via #1894.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/1351#event-1796365347
3.7 is out
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/1351#issuecomment-402060170
Splitting Python 2 and 3 as filetypes in Geany is whole another story.
Apart from the fact, that I don't think it's necessary at all. Except a very
few details, the syntax is identically regarding highlighting between Python 2
and Python 3. And in the long term, most people will write and
Could we at least distinguish between python2 and python3 relying on the
shebang line (if it exists) in order to highlight differently python2 source
files from python3 ones?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
> I meant adding them in the script not to be forgotten
So then its forgotten to remove the special handling years in the future when
3.7 is released :smile: Although the script could check versions its better to
KISS.
> I think that it is more likely that people have them in new code as
1. I meant adding them in the script not to be forgotten
2. That's up to you. I think that it is more likely that people have them in
new code as keywords than other way around.
Thanks for the workaround tip.
--
You are receiving this because you are subscribed to this thread.
Reply to this
Personally I would suggest not adding manually because:
1) manual additions are likely to be forgotten when the script @eht16 mentioned
gets run
2) since Geany does not know which Python is being used it will highlight async
and friends in old code where they are not keywords. Better to wait
Thanks for the info. Would it be possible to add `async` and `await` manually
for now and remove it in the future?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
In fact they are not meant to be keywords until Python 3.7, see [the
PEP](https://www.python.org/dev/peps/pep-0492/#deprecation-plans).
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
And the docs don't list them as keywords
https://docs.python.org/3/reference/lexical_analysis.html#keywords
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/1351#issuecomment-269560970
Patch to Scintilla isn't necessary. The list of keywords is maintained in
Geany. If you wish, you could create a patch for Scite but this is out of scope
of this project :).
Back to Geany: we have a script to automatically update the Python keywords
which basicalls asks the Python `keyword`
`async` and `await` are Python keywords since Python 3.5, however, they are not
highlighted as such in Geany.
--
You are receiving this because you are subscribed to this
12 matches
Mail list logo
