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

Rename the package to PyGMT #265

Merged
merged 3 commits into from
Jan 22, 2019
Merged

Rename the package to PyGMT #265

merged 3 commits into from
Jan 22, 2019

Conversation

leouieda
Copy link
Member

@leouieda leouieda commented Jan 22, 2019

GMT/Python is a bad name because it can't be translated into a
repository or Python package name easily. What we have now is a
repository called gmt-python, a website gmtpython, a package gmt,
and a PyPI package gmt-python. This is madness.
Since all other GMT Python wrappers are dead, we'll rebrand as PyGMT
(repo and packages will be pygmt).

This renames the package and imports so that the tests pass and the docs
build. I'm sure we'll find many references to gmt but we can fix those
with time.

Fixes #263

Reminders

  • Run make format and make check to make sure the code follows the style guide.
  • Add tests for new features or tests that would have caught the bug that you're fixing.
  • Add new public functions/methods/classes to doc/api/index.rst.
  • Write detailed docstrings for all functions/methods.
  • If adding new functionality, add an example to docstrings or tutorials.

GMT/Python is a bad name because it can't be translated into a
repository or Python package name easily. What we have now is a
repository called `gmt-python`, a website `gmtpython`, a package `gmt`,
and a PyPI package `gmt-python`. This is madness.
Since all other GMT Python wrappers are dead, we'll rebrand as PyGMT
(repo and packages will be `pygmt`).

This renames the package and imports so that the tests pass and the docs
build. I'm sure we'll find many references to `gmt` but we can fix those
with time.

Fixes #263
@leouieda leouieda merged commit a23f44a into master Jan 22, 2019
@leouieda leouieda deleted the rename branch January 22, 2019 18:39
weiji14 added a commit to weiji14/deepbedmap that referenced this pull request Feb 8, 2019
Couple of breaking changes. Since GenericMappingTools/pygmt#261, the conda-forge binary package is broken (hence all the recent CI build failures...) and we have to build the GMT binary from source, sigh. The new Dockerfile code for handling this isn't nice but it'll do for now.

Also, the Python `gmt-python` package has been renamed to `pygmt` in GenericMappingTools/pygmt#265, so the Pipfile is updated accordingly here. Also pinning to a newer git version on the upstream branch instead of my personal fork, since GenericMappingTools/pygmt#245 has been merged in!
@seisman seisman mentioned this pull request Feb 20, 2021
5 tasks
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.

Rename the project
1 participant