Hi @chrisburr,
The DIRAC (9.1 although probably others too) integration tests currently generate a lot of warnings from the M2Crypto constructor (the same two warnings for almost every bunch of tests):
ServerInstallDIR/diracos/lib/python3.11/site-packages/M2Crypto/__init__.py:34
/home/dirac/ServerInstallDIR/diracos/lib/python3.11/site-packages/M2Crypto/__init__.py:34: DeprecationWarning: Version._version is private and will be removed soon
if hasattr(__ver, u'_version'):
ServerInstallDIR/diracos/lib/python3.11/site-packages/M2Crypto/__init__.py:35
/home/dirac/ServerInstallDIR/diracos/lib/python3.11/site-packages/M2Crypto/__init__.py:35: DeprecationWarning: Version._version is private and will be removed soon
version_info = tuple(__ver._version[1])
I believe this is fixed in the latest M2Crypto (0.48.0): The version isn't strictly pinned here, but doesn't get updated as the conda-forge versions only go as high as 0.45.1. I note that you're the m2crypto-feedstock maintainer: Would it be possible to update it? Do you think updating is likely to cause any big problems for DIRAC? Is there anything I can do to help with this?
Regards,
Simon
Hi @chrisburr,
The DIRAC (9.1 although probably others too) integration tests currently generate a lot of warnings from the M2Crypto constructor (the same two warnings for almost every bunch of tests):
I believe this is fixed in the latest M2Crypto (0.48.0): The version isn't strictly pinned here, but doesn't get updated as the conda-forge versions only go as high as 0.45.1. I note that you're the m2crypto-feedstock maintainer: Would it be possible to update it? Do you think updating is likely to cause any big problems for DIRAC? Is there anything I can do to help with this?
Regards,
Simon