uvicorn 🚀 - windows support

Certainly the latest version (0.2) should, as there's no platform-specific stuff in there.

I don't know if there's any issues or not prior to that (or with 0.2 running under gunicorn) but happy to hear of any issues if you're seeing them

tomchristie on 29 Jun 2018

I have try to run under windows, there some stuff want to modify:

uvloop no support; want to use the default loop;
signals no support; disable UvicornWorker.init_signals and Server.set_signal_handlers

seewindcn on 11 Jul 2018

uvloop no support; want to use the default loop;

Okay, that's easy enough to do: --loop asyncio tho we might want to detect windows or pypy, and choose our loop and parser policies accordingly.

signals no support; disable UvicornWorker.init_signals and Server.set_signal_handlers

Okay, I've disable them in https://github.com/encode/uvicorn/pull/122
I've attempted to support catching Ctrl+C through signal.signal, but it's not clear to me if it's sufficient as implemented. (See https://stackoverflow.com/questions/24774980/why-cant-i-catch-sigint-when-asyncio-event-loop-is-running/24775107#24775107)

It's possible that we ought to start a new thread on windows specifically to catch signals.

tomchristie on 12 Jul 2018

Released as 0.2.10.

It'd be hugely helpful for anyone running on windows to try...

uvicorn app:app --loop asyncio

(Use the basic example app in the README to keep everything else simple)

And see if:

Does it start up okay now and serve requests? (If not what output do you see?)
Does it terminates okay on Ctrl+C events now? (What output do you see? Does nothing happen, or is it a clean termination, or is a python exception displayed?)
Can it be terminated by process explorer or whatever?

tomchristie on 12 Jul 2018

Hey @tomchristie, the installation on Windows fails because uvloop does not support Windows at the moment. Is there an option to install uvicorn without uvloop?

I found an ugly workaround of installing uvicorn with --no-dependencies and then installing every dependecy except uvloop manually.
Also worth noting that httptools requires a whole Visual Studio 2015 to build

Test results

I tested it on 64-bit Windows 10 Pro 1803 and Anaconda Python 3.6.5

Does it start up okay now and serve requests? (If not what output do you see?)

Yes, it works pretty well

Does it terminates okay on Ctrl+C events now? (What output do you see? Does nothing happen, or is it a clean termination, or is a python exception displayed?)

Yes, it terminates on Ctrl+C, not without an exception though:

(venv) C:\Users\ddkon\Projects\uvicorn-win-test>uvicorn app:App --loop asyncio
* Uvicorn running on http://127.0.0.1:8000 🦄 (Press CTRL+C to quit)
INFO: Started worker [10504]
INFO: 127.0.0.1 - "GET / HTTP/1.1" 200
INFO: 127.0.0.1 - "GET /favicon.ico HTTP/1.1" 200
INFO: 127.0.0.1 - "GET / HTTP/1.1" 200
INFO: 127.0.0.1 - "GET /favicon.ico HTTP/1.1" 200
INFO: 127.0.0.1 - "GET / HTTP/1.1" 200
INFO: 127.0.0.1 - "GET /favicon.ico HTTP/1.1" 200
INFO: 127.0.0.1 - "GET /what HTTP/1.1" 200
INFO: 127.0.0.1 - "GET /favicon.ico HTTP/1.1" 200
Traceback (most recent call last):
  File "c:\users\ddkon\anaconda3\Lib\runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "c:\users\ddkon\anaconda3\Lib\runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "C:\Users\ddkon\Projects\uvicorn-win-test\venv\Scripts\uvicorn.exe\__main__.py", line 9, in <module>
  File "c:\users\ddkon\projects\uvicorn-win-test\venv\lib\site-packages\click\core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "c:\users\ddkon\projects\uvicorn-win-test\venv\lib\site-packages\click\core.py", line 697, in main
    rv = self.invoke(ctx)
  File "c:\users\ddkon\projects\uvicorn-win-test\venv\lib\site-packages\click\core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "c:\users\ddkon\projects\uvicorn-win-test\venv\lib\site-packages\click\core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "c:\users\ddkon\projects\uvicorn-win-test\venv\lib\site-packages\uvicorn\main.py", line 50, in main
    server.run()
  File "c:\users\ddkon\projects\uvicorn-win-test\venv\lib\site-packages\uvicorn\main.py", line 142, in run
    self.loop.run_forever()
  File "c:\users\ddkon\anaconda3\Lib\asyncio\base_events.py", line 422, in run_forever
    self._run_once()
  File "c:\users\ddkon\anaconda3\Lib\asyncio\base_events.py", line 1396, in _run_once
    event_list = self._selector.select(timeout)
  File "c:\users\ddkon\anaconda3\Lib\selectors.py", line 323, in select
    r, w, _ = self._select(self._readers, self._writers, [], timeout)
  File "c:\users\ddkon\anaconda3\Lib\selectors.py", line 314, in _select
    r, w, x = select.select(r, w, w, timeout)
  File "c:\users\ddkon\projects\uvicorn-win-test\venv\lib\site-packages\uvicorn\main.py", line 145, in handle_exit
    self.logger.warning("Received signal {}. Shutting down.".format(sig.name))
AttributeError: 'int' object has no attribute 'name'

Can it be terminated by process explorer or whatever?

Yes, it is visible in Task Manager and I was able to terminate it from there

daniil-konovalenko on 13 Jul 2018

Wonderful, thanks so much! 😎😎😎

So ‘pip install uvicorn’ raises an error then?
Will have to think about how to handle that gracefully. Presumably setup.py could detect if it’s being installed on windows and adapt the requirements. (Running with ‘—loop uvloop —http h11’ would make sense.)

The Ctrl-C exception looks easy enough to resolve.

And thanks again, that’s super-helpful!

tomchristie on 13 Jul 2018

One other installation issue: Currently setup.py uses the built-in open to read README. This would likely cause problems in the majority of Windows machines, where the default system encoding cannot decode the Unicorn emoji. This is not difficult to resolve for a Python 3-only project—simply add encoding='utf8' to open.

Getting past that (I cloned and manually deleted the emoji), you’ll hit the uvloop support problem mentioned previously:

> pip install .\uvicorn\
Processing c:\users\uranusjr\documents\playground\uvicorn-play\uvicorn
Collecting click (from uvicorn==0.2.12)
  Using cached https://files.pythonhosted.org/packages/34/c1/8806f99713ddb993c5366c362b2f908f18269f8d792aff1abfd700775a77/click-6.7-py2.py3-none-any.whl
Collecting h11 (from uvicorn==0.2.12)
  Using cached https://files.pythonhosted.org/packages/f9/f3/8e4cf5fa1a3d8bda942a0b1cf92f87815494216fd439f82eb99073141ba0/h11-0.8.1-py2.py3-none-any.whl
Collecting httptools (from uvicorn==0.2.12)
  Using cached https://files.pythonhosted.org/packages/a3/75/40cdb732e8ef547d9f34ceb83c43ea7188c0ffb719ddc6a1ad160464292d/httptools-0.0.11.tar.gz
Collecting uvloop (from uvicorn==0.2.12)
  Using cached https://files.pythonhosted.org/packages/cd/e5/1492d3a6ee52f261df764eece684513bb8abbe988d4bd3d94093f39e2bea/uvloop-0.11.0.tar.gz
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "C:\Users\uranusjr\AppData\Local\Temp\pip-install-mlbym38h\uvloop\setup.py", line 15, in <module>
        raise RuntimeError('uvloop does not support Windows at the moment')
    RuntimeError: uvloop does not support Windows at the moment

uranusjr on 14 Jul 2018

Some additional information.

Running with Python 3.7, httptools does not require me the whole Visual Studio to build. Minimal VS 2017 Build Tools setup (toolkit v14.1, CRT SDK, and Windows 10 SDK) is enough for me to get it working. I didn’t test, but imagine the same would apply for 3.6 (which also supports VSBT 14.1) and 3.5 (VSBT 14.0 should work here).

Windows detection is straightforward with modern PEP 508 support. A simple change to the uvloop requirement into

"uvloop; platform_system!='Windows'",

And it installs for me 😃

I am not sure what’s the actual requirement of uvloop, but maybe os_name=='posix' or sys_platform!='win32' could be better markers.

uranusjr on 14 Jul 2018

👍1

I'm glad I could help!
Yeah, it does raise an error, such as the one that @uranusjr posted.
I was thinking that it might be a good idea to make uvloop an optional dependency (Yuri Selivanov strongly advises to). What do you think?

daniil-konovalenko on 14 Jul 2018

I’d like the behaviour to be that it’s used by default, but falls back to asyncio gracefully. We’re very close to that now - just need a few tweaks to setup.py and modify the defaulting behaviour in main.py a little

tomchristie on 14 Jul 2018

Okay, I think we should be looking much better now! 👍

Version 0.2.13 released, with fixes from #130

Anyone able to give it a whirl? 😄

tomchristie on 18 Jul 2018

I would strongly recommend using PEP 508 environment markers to specify dependencies instead. This allows for the same effect (in relatively recent Setuptools and pip), prevents the packager from needing to maintain platform-specific artifacts (e.g. wheels), and has immensely better compatibility with the new trend of locking-aware dependency management tools like Pipenv and Poetry.

The following should be functionality-wise equivalent to the if-elif-else clause:

requirements = [
    'click',
    'h11',
    'websockets>=6.0',
    "httptools; platform_system != 'Windows' and 'CYGWIN' not in platform_system and platform_python_implementation != 'PyPy'",
    "uvloop; platform_system != 'Windows' and 'CYGWIN' not in platform_system and platform_python_implementation != 'PyPy'",
]

uranusjr on 19 Jul 2018

Presumably things are problematic ATM, as we're importing httptools regardless of if it's installed or not.