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 package? #145

Open
JWCook opened this issue Nov 14, 2023 · 2 comments
Open

Rename package? #145

JWCook opened this issue Nov 14, 2023 · 2 comments
Labels
logistics CI Builds, deployments, packaging, project config, and other logistical details

Comments

@JWCook
Copy link
Member

JWCook commented Nov 14, 2023

"pyinaturalist-convert" is a bit of a mouthful. It's also a long name to type for imports (although its modules can also be imported from the pyinat namespace).

It might be worth renaming to something more concise. A few ideas off the top of my head:

  • pyinat-convert
  • pyinat-xform
  • pyinat-data
@JWCook JWCook added the logistics CI Builds, deployments, packaging, project config, and other logistical details label Nov 14, 2023
@arky
Copy link

arky commented Jan 24, 2024

As I mentioned in pyinat/pyinaturalist#542 (comment) Am leaning towards pyinat-utils

@JWCook
Copy link
Member Author

JWCook commented Jan 29, 2024

I try to avoid generic terms like "utils," because it's not very descriptive, and almost any code could be considered a utility. (But naming things is hard, so I have made a lot of "utils.py" type modules in the past!)

Right now the common thread in this library is converting between different observation/taxonomy data formats, so I'd like to stay with something in that theme. Any other ideas?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
logistics CI Builds, deployments, packaging, project config, and other logistical details
Projects
None yet
Development

No branches or pull requests

2 participants