-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
python version compatibilty #31
Comments
If you run python-minifier using python 3.7, the output will be compatible with 3.7 |
i'd have to test if 3.7 minified code works on 2.7, that would be a workaround. |
Python-minifier relies on the running interpreter for parsing, so it won't have greater compat than python itself. On that note, did you |
Is 3.10 support on the roadmap? |
@rochacbruno Yes. It's been implemented, but must be validated against the release version. If all goes well it will be released today 🤞. |
thanks @dflook I am bumping https://GitHub.com/rochacbruno/dynaconf to run CI on 3.10 and looks like the missing package is minify, we use it for our vendoring script. Thanks |
@rochacbruno python-minifier 2.5.0 is now available on PyPI with Python3.10 support |
Thanks @dflook now dynaconf install test on 3.10 is passing :) https://github.com/rochacbruno/dynaconf/runs/3816321083?check_suite_focus=true |
is there any reason for that edit never mind, I've seen this only now #94 |
hi,
i tried this to minify code that needs to run on python 2.7 and python 3.7
sadly print() gets translated to print if minifying is run on 2.7 which breaks compatibilty
exec(...) gets minified to: exec ... also triggering errors on 3.x
it would be nice if there was a compatibilty mode not downgrading all code to 2.x standard
best, index
The text was updated successfully, but these errors were encountered: