- 
                Notifications
    You must be signed in to change notification settings 
- Fork 3.4k
Fix for @4325--python2 testing not available on Github Actions. #4326
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| We can't maintain a target without testing so this PR should also remove the Python 2 target altogether | 
| 
 If we remove the target testing, then I don't think the next release can be 4.13.1. A "patch" version number change implies fixes to current features, i.e., Python2 targets. I can remove this code from the runtime/ directory, as well as similar directories (e.g., this,  Does anyone know why we are getting this non-deterministic build issue with masos? A build that is not robust in the face of timeouts, network errors, is a bug in itself. | 
| Yes I guess the next release would 4.14. | 
| Yes, looks easy.  | 
        
          
                doc/python-target.md
              
                Outdated
          
        
      | The examples from the ANTLR 4 book converted to Python are [here](https://github.com/jszheng/py3antlr4book). | ||
|  | ||
| There are 2 Python targets: `Python2` and `Python3`. This is because there is only limited compatibility between those 2 versions of the language. Please refer to the [Python documentation](https://wiki.python.org/moin/Python2orPython3) for full details. | ||
| There is ONE Python target: `Python3`. This is because there is only limited compatibility between those 2 versions of the language. Please refer to the [Python documentation](https://wiki.python.org/moin/Python3) for full details. | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess this can be rephrased a bit ?
        
          
                doc/python-target.md
              
                Outdated
          
        
      | ## Where can I get the runtime? | ||
|  | ||
| Once you've generated the lexer and/or parser code, you need to download the runtime. The Python runtimes are available from PyPI: | ||
| Once you've generated the lexer and/or parser code, you need to download the runtime. The Python runtime are available from PyPI: | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are -> is
| Thanks. I was about to Grammarly/ChatGPT the crap out of these files. I think I'll move the "Target Agnostic Format" into a completely different page. I now have some experience in getting target-agnostic working for all targets--probably more than anyone else. | 
| I rewrote the entire python-target.md file. 
 | 
| https://github.com/antlr/antlr4/pull/4326/checks?check_run_id=14489678593, and specifically: in every commit. This is a bit of unnecessary overhead. Git records the author name and email already in the commit. The author information is also in the /readme.md. The info is already all there.  The more I look at this, the more I think the DCO add-in doesn't work. | 
| I agree that the DCO add-in isn't clever enough. If you can propose a better solution I will likely support it :-) | 
| According to the DCO code, there is a isRequiredFor(author.login) test. Assuming  | 
| 
 | 
| I use SourceTreeEnvoyé de mon iPhoneLe 23 juin 2023 à 13:54, Ken Domino ***@***.***> a écrit :
-s -S are git command options. Git in itself is warped because there is so much authentication already happening. I have been using Github Desktop for commits (I flip among different front ends because they all suck). But, Github Desktop doesn't have a way to specify the -s -S options. desktop/desktop#5351 Blocked from using Github Desktop.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***> | 
| Let's move this DCO stuff to a conversation? | 
| 
 Yes, I also use SourceTree, but it also has issues, especially on Windows. They can't seem to get the UI working. But, there was something else, and I can't remember why I started using Github Desktop predominately for the last few months. | 
Signed-off-by: kaby76 <[email protected]>
Signed-off-by: kaby76 <[email protected]>
Signed-off-by: kaby76 <[email protected]>
Signed-off-by: kaby76 <[email protected]>
Signed-off-by: kaby76 <[email protected]>
| Closing and reopening as another PR because  | 
This PR fixes #4325.
This change removes the python2 target from Antlr. Github Actions removed support of any testing of Python 2.x on June 20, 2023. In addition, official support from python.org for 2.x stopped several years ago.
The instructions for the Python target have been updated with explicit code examples for a minimal parser driver, and the use of a visitor and listener to evaluate an expression of an expression grammar.