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

Harmonize, the capitalization -- PyLECO, PyLeco, pyleco,... #8

Closed
3 tasks done
BenediktBurger opened this issue Jul 22, 2023 · 4 comments
Closed
3 tasks done
Labels
documentation Improvements or additions to documentation

Comments

@BenediktBurger
Copy link
Member

BenediktBurger commented Jul 22, 2023

          Add some point we should decide on, and harmonize, the capitalization -- PyLECO, PyLeco, pyleco,...

Originally posted by @bilderbuchi in #7 (comment)

as the original name is LECO, PyLECO is a strong candidate.

PyLeco is like a Python class in CamelCase.

For consistency in naming within the LECO universe, I'm for PyLECO

ToDo:

  • rename Repository (shown name, not URL)
  • rename readme
  • rename all files
@BenediktBurger BenediktBurger mentioned this issue Jul 22, 2023
@bilderbuchi
Copy link
Member

To note, we don't gave to be 100% consistent -- the package name could easily be lower case pyleco, that seems common enough. But in text/docs, it would be good to choose one way and stick with it.

@BenediktBurger
Copy link
Member Author

BenediktBurger commented Jul 23, 2023 via email

@bilderbuchi
Copy link
Member

Agreed on both points.

@BenediktBurger
Copy link
Member Author

So:
Package name (for imports etc.): pyleco
Human name of the project (in docs etc.) : PyLECO

@BenediktBurger BenediktBurger added the documentation Improvements or additions to documentation label Oct 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants