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
uWSGI is used for interacting between server and django app. While django launches a test server when using locally that is not enough for running in production.
The solution will be to move it in a separate requirements file requirements-prod.txt until we have some better dependency management solution like pipenv
Last time I checked, none of the popular WSGI frameworks, viz, uWSGI or Gunicorn, support Windows due to the way they work. Ideally, uWSGI as a dependency should not be put in requirements.txt since it is not part of the application but is used to deploy WSGI applications.
uwsgi is installed by default using other means in the virtualenv
used by junction. There is no need to install uwsgi through the
application dependencies.
The support for uwsgi is flaky at best on Windows and works with
very limited functionality. Hence, this breaks development velocity
for people developing Junction on Windows.
Ref: pythonindia#651
Signed-off-by: Nabarun Pal <[email protected]>
Python version: 3.5
Windows 10 Pro, version: 1903
While running nox -- migrate --noinput for the first time, we are getting an issue saying
AttributeError: module 'os' has no attribute 'uname'
With quick googling, I could figure out that this is related to the package uwsgi==2.0.* in the requirements.txt
I removed this package from requirements.txt and tried running the command again and it worked.
Everything seems to work fine after this also. I am not sure about the purpose of this package, so I thought of putting this as an issue here.
Thanks,
The text was updated successfully, but these errors were encountered: