Add a table for compatibility of PyGMT with Python and GMT #763
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -207,6 +207,7 @@ Other Python wrappers for GMT: | |
|
|
||
| Documentation for other versions | ||
| -------------------------------- | ||
|
|
||
| * `Development <https://www.pygmt.org/dev>`__ (reflects the *master* branch on | ||
| GitHub) | ||
| * `Latest release <https://www.pygmt.org/latest>`__ | ||
|
|
@@ -216,3 +217,16 @@ Documentation for other versions | |
| * `v0.1.1 <https://www.pygmt.org/v0.1.1>`__ | ||
| * `v0.1.0 <https://www.pygmt.org/v0.1.0>`__ | ||
| * `v0.0.1a0 <https://www.pygmt.org/0.0.1a0>`__ | ||
|
|
||
| Compatibility with Python and GMT versions | ||
| ------------------------------------------ | ||
|
|
||
| ======= ========== ========= | ||
| 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 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. |
||
| 0.2.0 >=6.1.1 3.6 - 3.8 | ||
| 0.1.2 >=6.0.0 3.6 - 3.8 | ||
| 0.1.1 >=6.0.0 3.6 - 3.8 | ||
| 0.1.0 >=6.0.0 3.6 - 3.8 | ||
seisman marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| ======= ========== ========= | ||
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can add the 0.3.0 entry now or later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can release v0.3.0 two weeks before GMT v6.2.0 (late Jan or early Feb).