You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current name is complicated to remember and not fancy 😉
@j-stephan suggest caravanbashi, which is a leader of a caravan, see here. The name sounds fancy and we can it short it to bashi, which provides also the opportunity to do bad bash jokes 😄
Let's determine the effort to rename the package in the pypi registry.
The text was updated successfully, but these errors were encountered:
I checked, if it is possible to rename a project on pypi.org. The answer is no. The generic solution is to rename the project is:
Write to the readme, that the project has a new name.
Do a final release.
Rename the project in source code
Add the project with the old name as dependency
Register it with the new name
Because of issue #35 I would have to release version 2.0.0. I also thought also about some other API breaking improvements. I already wrote an prototype in PR #44. Therefore I need to touch nearly the whole code. An additional problem is, that sometimes not all valid pairs are generated. To verify, that the generator works correctly, I need to add a check if all valid pairs are generated. With increasing number of filter rules, the test needs to be modified, that it tests only valid pairs.
In sum, there is a lot of breaking stuff to do. So I decided to create a new repository with the name caravanbashi, copy the functionality from the repository piece by piece to the new repository with continuous testing and register and release it as new python package.
The current name is complicated to remember and not fancy 😉
@j-stephan suggest caravanbashi, which is a leader of a caravan, see here. The name sounds fancy and we can it short it to bashi, which provides also the opportunity to do bad bash jokes 😄
Let's determine the effort to rename the package in the pypi registry.
The text was updated successfully, but these errors were encountered: