Fixing issues related to pandas deprecation errors. Was required because Python 3.12 changed how pip works. Pandas resolved this, however our version limit on Pandas stopped this from being updated, meaning that PolarRoute was spitting out many warnings with Python 3.12. Some of these have been fixed, but the SettingWithCopyWarning still exists, and will become deprecated by the time Pandas 3.0 comes out. We should push the refactored route planning by then so I don't think it's worth pursuing fixing these for now.
Fixes:
(MeshiPhi issue #37 is most related)
Testing
To ensure that the functionality of the PolarRoute codebase remains consistent throughout the development cycle a testing strategy has been developed, which can be viewed in the document test/testing_strategy.md.
This includes a collection of test files which should be run according to which part of the codebase has been altered in a pull request. Please consult the testing strategy to determine which tests need to be run.
[ ] My changes have not altered any of the files listed in the testing strategy
[x] My changes result in all required regression tests passing without the need to update test files. Passing reg tests
[ ] My changes require one or more test files to be updated for all regression tests to pass.
PolarRoute Pull Request Template
Date: 2024-03-26 Version Number: 0.4.0
Description of change
Fixing issues related to pandas deprecation errors. Was required because Python 3.12 changed how pip works. Pandas resolved this, however our version limit on Pandas stopped this from being updated, meaning that PolarRoute was spitting out many warnings with Python 3.12. Some of these have been fixed, but the SettingWithCopyWarning still exists, and will become deprecated by the time Pandas 3.0 comes out. We should push the refactored route planning by then so I don't think it's worth pursuing fixing these for now.
Fixes:
(MeshiPhi issue #37 is most related)
Testing
To ensure that the functionality of the PolarRoute codebase remains consistent throughout the development cycle a testing strategy has been developed, which can be viewed in the document
test/testing_strategy.md. This includes a collection of test files which should be run according to which part of the codebase has been altered in a pull request. Please consult the testing strategy to determine which tests need to be run.[ ] My changes have not altered any of the files listed in the testing strategy
[x] My changes result in all required regression tests passing without the need to update test files.
Passing reg tests
[ ] My changes require one or more test files to be updated for all regression tests to pass.
Checklist
0.4.xbranch (DO NOT SUBMIT A PR TO MAIN)