[BUG] Namespace conflict with scikit's ninja

[Lrakotoson]

Describe the bug

django-ninja uses the same namespace as the scikit build ninja package.
When it is needed for both to work on the same environment, this conflict causes:

• the last installed to overwrite the files of first in site-packages
• the namespace conflict: import ninja; from ninja import xxx

What did not work

Separate directory installation: poetry or pip custom path, manual package folder renaming.
This did not work as django-ninja uses itself the namespace ninja, so internal import are broken.
This cannot, practically, be done the other way (eg: changing ninja to scikit_ninja) as there are more packages depending on ninja than django-ninja (which is also higher level).

What did work for now

Changing django-ninja namespace: in a local fork, I changed every occurrence of ninja to django_ninja

Versions:

• Python version: 3.12
• Django version: 5.1
• Django-Ninja version: 1.3.0
• Pydantic version: 2.10.3

[baseplate-admin]

This sounds more of a python issue to me than django-ninja

I dont think adding relative import in a pythonic codebase is good