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

Cope with numpy-1.24 type symbol deprecations #52

Merged
merged 2 commits into from
Dec 21, 2022
Merged

Cope with numpy-1.24 type symbol deprecations #52

merged 2 commits into from
Dec 21, 2022

Conversation

neilflood
Copy link
Member

This now passes standard tests under numpy-1.24.0.

@neilflood
Copy link
Member Author

Dammit, a typo in the commit message - I hate that......

@gillins
Copy link
Member

gillins commented Dec 21, 2022

Should we also be coping with int64/uint64 (not sure why we didn't do this earlier). And the int8 support coming to GDAL soon (https://gdal.org/development/rfc/rfc87_signed_int8.html)....

@gillins
Copy link
Member

gillins commented Dec 21, 2022

Dammit, a typo in the commit message - I hate that......

You can edit the title of this PR at least. When you do a squash and merge the originally commit message will be lost anyway.

@neilflood neilflood changed the title Cope with numpy-1.12 type symbol deprecations Cope with numpy-1.24 type symbol deprecations Dec 21, 2022
@neilflood
Copy link
Member Author

I think we do already cope with int64/uint64. There is a little extra couple of lines to add to that list, if gdalconst has GDT_Int64.

Thanks, edited the title, at least :-)

@neilflood
Copy link
Member Author

By the way, I also tested these changes under numpy-1.23, and it works fine there, too.

@neilflood neilflood merged commit bd1b08c into ubarsc:master Dec 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants