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

Difference between the name on pypi and the name of the module #97

Closed
luzfcb opened this issue Sep 21, 2014 · 5 comments
Closed

Difference between the name on pypi and the name of the module #97

luzfcb opened this issue Sep 21, 2014 · 5 comments

Comments

@luzfcb
Copy link

luzfcb commented Sep 21, 2014

Although I have followed "everything" as the documentation, nothing worked properly.

After racking my brain for some time, I discovered my mistake.
I had installed the wrong package, they just ran pip install djangular, and a package[1] created by another developer was installed.

I think the module of this package Should be renamed to django_angular. This would avoid confusion stupid like that, and to facilitate that IDE's like PyCharm detect and install the correct package.

In short, I believe the pypi package name and the module name must be the same.

[1] https://pypi.python.org/pypi/djangular/0.2.7
[2] https://pypi.python.org/pypi/django-angular/0.7.6

@jrief
Copy link
Owner

jrief commented Sep 21, 2014

For me, django_angular seemed too verboose. I didn't want to have "django" in a Django app.

Please participate in the survey for naming conventions. There will be some changes for 0.8.0. So add yours.

@luzfcb
Copy link
Author

luzfcb commented Sep 21, 2014

@jrief
I made the suggestion to django_angular[2] because djangular[1] is already being used.

the two django packages, djangular[1] and django_angular[2] have the same application name, but different names in pypi.

I thought this[2] project be simpler to change the name due to another[1] project to be older than this, although much less used.

The idea is simple. Not cause confusion in new users.

Ok, I will participate of the survey for naming conventions

[1] https://pypi.python.org/pypi/djangular/0.2.7
[2] https://pypi.python.org/pypi/django-angular/0.7.6

@merwok
Copy link

merwok commented Nov 19, 2014

For me, django_angular seemed too verboose. I didn't want to have "django" in a Django app.

That is the Django convention, and one that grieves me. After installing a django-whatever package, I have to find that the actual module name is, and it’s often something much too generic like “comments” or “cms”. That, coupled with the fact that references to apps don’t use fully-qualified Python names (i.e. “blog” instead of “project.apps.blog”), and good luck when you get a naming conflict.

In the Pyramid world, we pip install pyramid-whatever, and then we import pyramid_whatever. It works well.

@adrienbrunet
Copy link
Collaborator

Module name will be updated with the new release.

@adrienbrunet
Copy link
Collaborator

Cf ticket #239

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

No branches or pull requests

4 participants