You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just wanted to give anyone interested a heads up on the next few updates coming for Transcrypt. Since 3.9.3 was released, I now have 3.9.4 almost ready to go that includes more fixes and features, and moves the behavior of some built-ins closer to that of CPython.
At the same time there have been a few PRs submitted, most notably by @JGreenlee, that I can't get to right away due to current obligations, but do appreciate them and will be looking at them soon. After 3.9.4 is released, I want to particularly incorporate #879 that fixes the prototype pollution issue as its own 3.9.5 release, barring any issues with it. If anyone else has input on that, please add to the discussion.
Soon after that I need to get to work on updating the Transcrypt compiler itself to work with a newer version of Python since 3.9 is at EOL next year. I want to get that out ideally by the end of this year, but no later then Q1 of next year. I will probably target AST compatibility with Python 3.12
On a more general note, I am really trying to keep @JdeH 's original philosophies about Transcrypt under consideration whenever updates are made. Specifically:
Keep the runtime module as small as possible
This may mean that some features available in CPython will not be implemented and will remain a limitation of Transcrypt
Keep the JS runtime performant
Adhere to CPython behavior as much as possible
(but practicality beats purity in some cases)
That said, if anyone sees an update that goes against these principles, please let me know so it can be discussed. Inevitably, any feature adds will likely work against these goals, so some decisions will always need to be made on value over cost.
As a freelance developer, I have to balance working on Transcrypt with keeping my bills paid, so my timing with working on this isn't always consistent. But I have a strong affinity for this project and will continue to keep it moving forward.
Thanks,
John S.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I just wanted to give anyone interested a heads up on the next few updates coming for Transcrypt. Since 3.9.3 was released, I now have 3.9.4 almost ready to go that includes more fixes and features, and moves the behavior of some built-ins closer to that of CPython.
At the same time there have been a few PRs submitted, most notably by @JGreenlee, that I can't get to right away due to current obligations, but do appreciate them and will be looking at them soon. After 3.9.4 is released, I want to particularly incorporate #879 that fixes the prototype pollution issue as its own 3.9.5 release, barring any issues with it. If anyone else has input on that, please add to the discussion.
Soon after that I need to get to work on updating the Transcrypt compiler itself to work with a newer version of Python since 3.9 is at EOL next year. I want to get that out ideally by the end of this year, but no later then Q1 of next year. I will probably target AST compatibility with Python 3.12
On a more general note, I am really trying to keep @JdeH 's original philosophies about Transcrypt under consideration whenever updates are made. Specifically:
This may mean that some features available in CPython will not be implemented and will remain a limitation of Transcrypt
(but practicality beats purity in some cases)
That said, if anyone sees an update that goes against these principles, please let me know so it can be discussed. Inevitably, any feature adds will likely work against these goals, so some decisions will always need to be made on value over cost.
As a freelance developer, I have to balance working on Transcrypt with keeping my bills paid, so my timing with working on this isn't always consistent. But I have a strong affinity for this project and will continue to keep it moving forward.
Thanks,
John S.
Beta Was this translation helpful? Give feedback.
All reactions