* Updating subprocess.pyi to support python 3.5
Also added DEVNULL which was added in 3.3
* Incorrectly checked sys.version_info
* Addressed travis build failures
Forgot that __init__ should return None and also forgot "self" on a method. Like a dummy.
typing.AnyStr usage here was a mistake that I noticed too late,
from a GitHub comment[1]:
AnyStr is a type variable so in your version of
objectify.fromstring() the types if text and base_url have to
correspond -- but with unions they can each be either str or bytes,
and that's how the rest of the API is defined.
[1] https://github.com/python/typeshed/pull/436#issuecomment-237708512
To be on the conservative side I'm making it an Iterable of values;
this should be good enough for common usages.
The types of the values actually correspond to the types of the
argument ContextManagers, but a proper signature would require
variadic type variables (https://github.com/python/typing/issues/193),
which isn't worth waiting for. :-)
First was for mypy compatibility, but is no longer needed.
Second is removed by going inheriting (Iterable[bytes],
Container[bytes], Sized, Reversible[bytes]) instead of
Sequence[bytes]. Should presumably catch more errors when using __getattr__
* py3 done
* have to have specific version, to much changes
* py2 done
* merge py2 and py3 version
* fix duplicate definition in mypy
* apply version specific def
* rename ContextManager, single line for import
From the BaseRequestHandler documentation:
handle()
This function must do all the work required to service a request.
The default implementation does nothing. Several instance attributes
are available to it; the request is available as self.request; the
client address as self.client_address; and the server instance as
self.server, in case it needs access to per-server information.
The type of self.request is different for datagram or stream
services. For stream services, self.request is a socket object;
for datagram services, self.request is a pair of string and
socket.
Mainly reorder the stub, adding some missing method and having some other being version dependent.
I've also, in 30f395e, specialized some function, specifying it for Sequence and Mapping, which is not strictly correct (because any class having `__getitem__` should get accepted) but is way more useful that simply having Any.
