Originally created by @tcztzy on GitHub (May 1, 2024).
Is your feature request related to a problem? Please describe.
Publish this project to Pypi.org using namespace package.
Describe the solution you'd like
Once it is publish as a namespace like open_webui, then third party developer can publish their package like open_webui.apps.<my_app>
Describe alternatives you've considered
No
Additional context
No
Originally created by @tcztzy on GitHub (May 1, 2024).
**Is your feature request related to a problem? Please describe.**
Publish this project to Pypi.org using [namespace package](https://packaging.python.org/en/latest/guides/packaging-namespace-packages/).
**Describe the solution you'd like**
Once it is publish as a namespace like `open_webui`, then third party developer can publish their package like `open_webui.apps.<my_app>`
**Describe alternatives you've considered**
No
**Additional context**
No
I can contribute but It will rename the top level backend directory to open-webui, would you accept such a big change? And we also need a Pypi organization account.
@tcztzy commented on GitHub (May 6, 2024):
I can contribute but It will rename the top level `backend` directory to `open-webui`, would you accept such a big change? And we also need a [Pypi organization account](https://docs.pypi.org/organization-accounts/).
apps/utils/constants/config are very common module names and will conflict with other packages.
@tcztzy commented on GitHub (May 6, 2024):
it can be done without renaming the directory, but renaming the python imports is required in most cases. For example
https://github.com/open-webui/open-webui/blob/30b053116d6a40fc60dad1766e83ed41ffcb712c/backend/main.py#L20
should be refactored as
```python
from open_webui.apps.ollama.main import app as ollama_app
```
and
https://github.com/open-webui/open-webui/blob/30b053116d6a40fc60dad1766e83ed41ffcb712c/backend/main.py#L38
should be refactored as
```python
from open_webui.utils.utils import get_admin_user
```
`apps`/`utils`/`constants`/`config` are very common module names and will conflict with other packages.
Maybe we should publish it firstly, use pipx will install package separated from other, therefore name conflict is not a big problem
@tcztzy commented on GitHub (May 13, 2024):
Maybe we should publish it firstly, use `pipx` will install package separated from other, therefore name conflict is not a big problem
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @tcztzy on GitHub (May 1, 2024).
Is your feature request related to a problem? Please describe.
Publish this project to Pypi.org using namespace package.
Describe the solution you'd like
Once it is publish as a namespace like
open_webui, then third party developer can publish their package likeopen_webui.apps.<my_app>Describe alternatives you've considered
No
Additional context
No
@tjbck commented on GitHub (May 4, 2024):
Github workflow PR welcome!
@tcztzy commented on GitHub (May 6, 2024):
I can contribute but It will rename the top level
backenddirectory toopen-webui, would you accept such a big change? And we also need a Pypi organization account.@tjbck commented on GitHub (May 6, 2024):
If we can rename the
backenddirectory during our workflow that would be ideal.@tcztzy commented on GitHub (May 6, 2024):
it can be done without renaming the directory, but renaming the python imports is required in most cases. For example
https://github.com/open-webui/open-webui/blob/30b053116d6a40fc60dad1766e83ed41ffcb712c/backend/main.py#L20
should be refactored as
and
https://github.com/open-webui/open-webui/blob/30b053116d6a40fc60dad1766e83ed41ffcb712c/backend/main.py#L38
should be refactored as
apps/utils/constants/configare very common module names and will conflict with other packages.@tcztzy commented on GitHub (May 13, 2024):
Maybe we should publish it firstly, use
pipxwill install package separated from other, therefore name conflict is not a big problem@tjbck commented on GitHub (May 14, 2024):
I'll prioritise this in the near future!