-
Notifications
You must be signed in to change notification settings - Fork 3
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
Fix for compatibility with pyuvdata 3.0 and numpy 2.0 #669
Open
bhazelton
wants to merge
11
commits into
main
Choose a base branch
from
fix_pyuvdatav3
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #669 +/- ##
==========================================
+ Coverage 98.26% 98.28% +0.02%
==========================================
Files 34 34
Lines 5304 5308 +4
==========================================
+ Hits 5212 5217 +5
+ Misses 92 91 -1 ☔ View full report in Codecov by Sentry. |
bhazelton
force-pushed
the
fix_pyuvdatav3
branch
from
September 27, 2024 16:18
97f3ef3
to
3e894e4
Compare
for more information, see https://pre-commit.ci
for support for numpy v2.0
drop deprecated mamba stuff
bhazelton
force-pushed
the
fix_pyuvdatav3
branch
from
September 27, 2024 19:10
a02ad0a
to
9eea675
Compare
bhazelton
force-pushed
the
fix_pyuvdatav3
branch
from
November 7, 2024 00:01
7466b0a
to
70300a8
Compare
bhazelton
changed the title
Fix for compatibility with pyuvdata v3.0
Fix for compatibility with pyuvdata 3.0 and numpy 2.0
Nov 7, 2024
This warning doesn't show up except when running pytest with the `-W error` option. It's handled and doesn't indicate a real problem. It's quite unpredictable which test it will happen in. Also try to use context managers as much as possible and fix a couple other test issues.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
psycopg
) for numpy 2.0 compatibility. This requires sqlalchemy>=2.0 and python>=3.10Motivation and Context
Types of changes
Checklist:
Other:
changes when this is merged.