-
Notifications
You must be signed in to change notification settings - Fork 110
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
Python3 safe division #274
Conversation
…turize -wn -2 --nofix=division_safe **/**/*.py
…e **/*.py; futurize -wn --fix=division_safe **/**/*.py
Honestly I didn't even run the test on this PR. |
Nice! Note that |
I will try to run the tests a bit later on Stage 2 without division. If they pass, then we can add |
I ran the tests again without the @siscia I think it would be a good idea to get all your commits except the Stage 2 ones merged as soon as possible (*). Then we can "futurize" and validate individual files on a case-by-case basis, until they all support Python 3. But if we futurize everything at once, I fear we will introduce more silent breakage. (*) We also need to keep in mind that indentations changes etc. will cause a lot of conflicts when rebasing, so if anyone has a long-lived feature branch lying around, it might be a good idea to get it merged ASAP. Maybe we could make an announcement on the mailing list? |
After a few fixes (cf. #272), dark photon tests pass too. |
#275 defaults to using real division in physics models. |
@siscia Can you open a new PR with just the pickler trick? Thanks! |
Please don't ask me to do it... You can just copy the new pickler and make a PR yourself... |
Ok, I'll cherry-pick your commit |
Many thanks! :) |
outdated |
PR as discussed in #270