Add a table for compatibility of PyGMT with Python and GMT#763
Add a table for compatibility of PyGMT with Python and GMT#763
Conversation
|
|
||
| ======= ========== ========= | ||
| PyGMT GMT Python | ||
| ======= ========== ========= |
There was a problem hiding this comment.
We can add the 0.3.0 entry now or later.
There was a problem hiding this comment.
Let's add it later, not too sure yet when we want to cut a 0.3.0 release?
There was a problem hiding this comment.
I think we can release v0.3.0 two weeks before GMT v6.2.0 (late Jan or early Feb).
README.rst
Outdated
| ======= ========== ========= | ||
| PyGMT GMT Python | ||
| ======= ========== ========= | ||
| 0.2.1 >=6.1.1 3.6 - 3.9 |
There was a problem hiding this comment.
Since we went no-arch in v0.2.1 (see #690), should the Python compatibility be >=3.6? Not sure how to test on Python 3.10 but it should technically work.
There was a problem hiding this comment.
Do Python 3.6 codes always work with future Python versions?
There was a problem hiding this comment.
It should? I think async/await became reserved names in 3.7 but PyGMT doesn't use those, or any advanced stuff really. Things should be safe until Python 4 at least.
Description of proposed changes
Fixes #748.
Reminders
make formatandmake checkto make sure the code follows the style guide.doc/api/index.rst.Notes
/formatin the first line of a comment to lint the code automatically