-
Notifications
You must be signed in to change notification settings - Fork 111
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
Retire cmp() function #498
Conversation
If there are no concerns I'll merge this on the coming weekend |
Markus,
We'd prefer that you not touch files that were created at LBNL. Now that
you've raised the issue we are studying it and will check in a
CCTBX-centric solution to the problem. We do not believe your proposed
changes preserve function, but we need more time to really investigate and
sort things out.
Nick
Nicholas K. Sauter, Ph. D.
Senior Scientist, Molecular Biophysics & Integrated Bioimaging Division
Lawrence Berkeley National Laboratory
1 Cyclotron Rd., Bldg. 33R0345
Berkeley, CA 94720
(510) 486-5713
…On Wed, Jul 15, 2020 at 8:45 AM Markus Gerstel ***@***.***> wrote:
If there are no concerns I'll merge this on the coming weekend
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#498 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADQ24VT4KEWQOPMYY6GZQWLR3XFJ3ANCNFSM4OXHKKDQ>
.
|
Dear Nick, good to hear from you. I have raised this issue previously (#493) however as I haven't had any response I went ahead and prepared this patchset, as suggested by our official CCTBX contribution guidelines, https://github.com/cctbx/cctbx_project/blob/master/CONTRIBUTING.md. In fact, you will find I followed those to the letter. I followed local code styles and did not touch anything unrelated to the issue at hand. I explicitly preserved even the (most certainly unused) leftover helper functions, as pointed out in the pull request, to avoid any interface breakages. All 95 test suites were successfully run on the pull request - as indicated by the 95 green ticks. So please forgive me when I am a bit confused about where you see any potential issues. Obviously I'm happy for you to review and validate my changes and await your constructive and timely feedback. I would of course also gladly review any alternative pull requests. Best wishes -Markus |
I'll have more time next week to look through this, but here are a few points based on a cursory look.
|
I've made the requested changes. It would be great to get this in because the deprecation warnings are making it difficult to spot real issues: |
Rebasing onto master should fix the XFEL CI tests. |
Ah, I see the XFEL CI tests are run twice, once on the branch which is behind master, and once on the merged code (near the bottom of the list) where they are passing. No worries then. |
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.
There are still a few duplicate cmp
implementations.
Looks good, thanks! |
Thank you for the review! |
I rewrote all places where
cmp
is used and removed thecmp
import.In the interest of maximum compatibility I did not remove the declarations of the following functions that are now no longer needed, but are declared in public namespaces:
cctbx_project/cctbx/euclidean_model_matching.py
Lines 251 to 252 in 62adfcc
cctbx_project/cctbx/euclidean_model_matching.py
Lines 465 to 466 in 62adfcc
cctbx_project/cctbx/sgtbx/__init__.py
Lines 832 to 833 in 62adfcc
cctbx_project/cctbx/sgtbx/direct_space_asu/check_redundancies.py
Lines 237 to 238 in 62adfcc
Background:
The
cmp
function is gone. Importing it frompast
(which is part of thefuture
package) is causing deprecation warnings all over the place due to PythonCharmers/python-future#551. Theimp
module will be removed in Python 3.10.This also -as far as I can tell- would allow retiring the dependency on the
future
package. This is a good thing as thefuture
package is a bit special.Closes #493