-
Notifications
You must be signed in to change notification settings - Fork 26
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
Prepare for version 2.5.0 release #550
Conversation
Codecov Report
@@ Coverage Diff @@
## dev #550 +/- ##
=======================================
Coverage 84.73% 84.73%
=======================================
Files 39 39
Lines 7985 7985
Branches 1693 1693
=======================================
Hits 6766 6766
Misses 883 883
Partials 336 336 Continue to review full report at Codecov.
|
There are three new test failures in PyNWB:
|
These succeed here but fail in pynwb when hdmf-common is imported. Still worth adding to HDMF
Before release, there are two issues to be resolved:
See #584 which should resolve it. And two tests:
where the AlignedDynamicTable spec that is loaded locally has its inherited 'id' and VectorData columns resolved (included) whereas the spec cached in the file does not. Interestingly, this does not happen when running this test in hdmf-common only. It seems to happen only because NWB includes HDMF-common. |
#547 can be addressed by setting a max version for ruamel.yaml that does not show the PendingDeprecationWarning, or if time permits, migrating the to-be-deprecated calls to the new format. It should be addressed in this release because it clutters the output on I/O and may confuse users. |
Is this going to be part of another PR? |
These errors are addressed in NeurodataWithoutBorders/pynwb#1354 |
Some critical bugs were identified with the experimental namespace and class generation. Ideally, these will be resolved before this release.CI notes:
ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 88 from C header, got 80 from PyObject
. Upgrading to numpy 1.20 solves the issue but numpy 1.20 does not support Python 3.6, which we want to continue to support. For this reason, the python3.9 job fails. So users should note that when using Python 3.9 (which is not fully supported by HDMF), they should install a version of numpy first, and then build the wheels for h5py 2.10.