Replies: 3 comments 4 replies
-
Do you plan to use pyupgrade? |
Beta Was this translation helpful? Give feedback.
1 reply
-
Sounds like a good approach. I am interested in helping out with the transition. |
Beta Was this translation helpful? Give feedback.
0 replies
-
@chanicpanic Your offer to help is much appreciated. I've created an initial branch+PR: #925 I will probably make more changes in the coming week. The remaining tasks, that I'm aware of: Tasks remaining:
|
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We've had a few discussions on the topic before, but now I've grown convinced that Lark should drop Python 2 support for the main development branch.
We can still backport support for critical fixes, but Lark is pretty stable already.
Since this is a major backwards-incompatible change, it might be a good opportunity to also move into a backwards-incompatible version 1, that will also fix a lot of the interface inconsistencies that Lark has accumulated over the years.
Is anyone interested in helping with this?
Any other thoughts on the subject?
Beta Was this translation helpful? Give feedback.
All reactions