New submission from Jaap van der Velde :
When running:
```
datetime.strptime('2013 23', '%Y %W')
```
The result is `datetime.datetime(2013, 1, 1, 0, 0)`. When running:
```
datetime.strptime('2013 23 1', '%Y %W %w')
```
The result is `datetime.datetime(201
Jaap van der Velde added the comment:
Breaking the API isn't good, but it will only break if log_message doesn't
*receive* all messages, because that's what people who override it count on.
If there's some way of detecting who called log_message, you could use the
appr
Jaap van der Velde added the comment:
Closing and not fixing is fair enough - I did not realize that this would be an
issue that occurs in many places in stdlib.
I realize this is not a help forum, so I will ask elsewhere to see if there's
some way to redirect all of sys.stderr in scen
New submission from Jaap van der Velde:
On line 556 of server.py, the sys.stderr.write assumes that sys.stderr is
assigned and not None.
However, when developing Windows services using the pypiwin32 library (as an
example), sys.stderr == None
A workaround is to override the log_message
