Skip to content
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

Extending support to biopython>1.79 #1723

Closed
ojeda-e opened this issue Aug 3, 2023 · 8 comments
Closed

Extending support to biopython>1.79 #1723

ojeda-e opened this issue Aug 3, 2023 · 8 comments

Comments

@ojeda-e
Copy link

ojeda-e commented Aug 3, 2023

Hello ProDy developers.

I have been working with your package and we are trying to stay updated with dependencies. Recently I bumped ProDy to 2.4.0 and found out that it depends on biopython<=1.79. Effectively, in your setup.py biopython is restricted to <=1.79 (added in d65a4c1).

I am certain you have strong reasons to pin the version of Biopython. However, I was wondering if ProDy devs have any plans of extending support for ProDy in higher versions of Biopython in the short term. Thanks!

@jamesmkrieger
Copy link
Contributor

Hello, yes, I think this should be fine. I think the main thing that affected us in the shift to 1.80 was the loss of pairwise2 but we now have a way to handle that, so it should be fine. We’ll have to try it and see.

@ojeda-e
Copy link
Author

ojeda-e commented Aug 4, 2023

Thanks fro your quick reply @jamesmkrieger, looking forward to it!

@jamesmkrieger
Copy link
Contributor

Of course, everything is always more complicated than one would think. The output from alignment has some different format in later biopython versions so we'll have to look into what the differences are and change some functions that use it.

@jamesmkrieger
Copy link
Contributor

I have tested everything now and there was something to fix in #1816 but now I think we're there once it passes the tests and is merged

@merkys
Copy link

merkys commented Jan 22, 2024

I tried building bb2b63f with biopython 1.81 and it failed testBuildMSAlocal with the following on both Python 3.11 and 3.12:

======================================================================
FAIL: testBuildMSAlocal (prody.tests.sequence.test_analysis.TestBuildMSA.testBuildMSAlocal)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/merkys/ProDy/.pybuild/cpython3_3.11_prody/build/prody/tests/sequence/test_analysis.py", line 1210, in testBuildMSAlocal
    assert_array_equal(expect, result)
  File "/usr/lib/python3/dist-packages/numpy/testing/_private/utils.py", line 985, in assert_array_equal
    assert_array_compare(operator.__eq__, x, y, err_msg=err_msg,
  File "/usr/lib/python3.11/contextlib.py", line 81, in inner
    return func(*args, **kwds)
           ^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/numpy/testing/_private/utils.py", line 862, in assert_array_compare
    raise AssertionError(msg)
AssertionError: 
Arrays are not equal

Mismatched elements: 2 / 2 (100%)
 x: array([<Sequence: 1 (msa_3hsyA_3o21A[0]; length 380; 354 residues and 26 gaps)>,
       <Sequence: 2 (msa_3hsyA_3o21A[1]; length 380; 374 residues and 6 gaps)>],
      dtype=object)
 y: array([<Sequence: 1 (Unknown[0]; length 80; 59 residues and 21 gaps)>,
       <Sequence: 2 (Unknown[1]; length 80; 64 residues and 16 gaps)>],
      dtype=object)

@merkys
Copy link

merkys commented Jan 22, 2024

Sorry, I assumed #1816 is merged, will try building #1816.

@jamesmkrieger
Copy link
Contributor

Sorry, I assumed #1816 is merged, will try building #1816.

ok, sounds good.

I'm sorry that it isn't yet. I was waiting for someone to try writeMMTF

@jamesmkrieger
Copy link
Contributor

I've tested writeMMTF enough now and merged it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants