Jan-Philip Gehrcke added the comment:
Hello!
Like everybody in this thread I would love to see this land and have prepared a
new patch, hoping that we can process this still for 3.6.
Antoine summarized the core task here very well:
> Let's stay focused on what is
> necessary to
Jan-Philip Gehrcke added the comment:
Windows is the only Python-supported platform where utime did not work for
directories, ages ago, right?
If that is the case, I support Larry Hastings' approach of removing the entire
sentence:
"Whether a directory can be given for path
Changes by Jan-Philip Gehrcke :
--
keywords: +patch
Added file: http://bugs.python.org/file37979/issue20709_py27.patch
___
Python tracker
<http://bugs.python.org/issue20
Changes by Jan-Philip Gehrcke :
Added file: http://bugs.python.org/file37980/issue20709_tip.patch
___
Python tracker
<http://bugs.python.org/issue20709>
___
___
Python-bug
Jan-Philip Gehrcke added the comment:
I have added patches for the documentation, where I removed the sentence in
question and re-wrapped the paragraph.
--
___
Python tracker
<http://bugs.python.org/issue20
Jan-Philip Gehrcke added the comment:
For Python 2.7, we will not change behavior, even if unexpected. Instead, the
sys.exit-docs should be adjusted and
- warn about the fact that nothing is written to stderr
if sys.exit(msg) gets called from a non-primary thread, and
- note
Changes by Jan-Philip Gehrcke :
Removed file: http://bugs.python.org/file19006/thread_sys_exit_test.py
___
Python tracker
<http://bugs.python.org/issue6634>
___
___
Pytho
Jan-Philip Gehrcke added the comment:
For Python 3.5, I have attached a patch that
- adds relevant test cases to test_threading.py which probe
the interpreter's stderr output for compliance with what
the docs state.
- makes sys.exit(msg) write msg to stderr, even if c
Changes by Jan-Philip Gehrcke :
Added file: http://bugs.python.org/file37988/issue6634_py35.patch
___
Python tracker
<http://bugs.python.org/issue6634>
___
___
Python-bug
Changes by Jan-Philip Gehrcke :
Removed file: http://bugs.python.org/file37986/issue6634_py35.patch
___
Python tracker
<http://bugs.python.org/issue6634>
___
___
Pytho
Changes by Jan-Philip Gehrcke :
Removed file: http://bugs.python.org/file37988/issue6634_py35.patch
___
Python tracker
<http://bugs.python.org/issue6634>
___
___
Pytho
Jan-Philip Gehrcke added the comment:
> Regarding the documentation patch: I like to start sentences
> with a capital letter. Perhaps change it to start
> “Calling :func:`exit` only terminates . . .”.
Thanks for feedback. Have now used "Invocation of " to not repeat "
Changes by Jan-Philip Gehrcke :
Removed file: http://bugs.python.org/file37983/issue6634_py27.patch
___
Python tracker
<http://bugs.python.org/issue6634>
___
___
Pytho
Changes by Jan-Philip Gehrcke :
Added file: http://bugs.python.org/file37990/issue6634_py27.patch
___
Python tracker
<http://bugs.python.org/issue6634>
___
___
Python-bug
Jan-Philip Gehrcke added the comment:
Thanks for your feedback Antoine.
> I'm not sure what the doc patch achieves.
Let me try to bring things in order. It should achieve two things:
1. Properly describe the stderr-writing behavior of
Jan-Philip Gehrcke added the comment:
First, I want to address the situation in 2.7. Please have a look at my patch
and my reasoning.
This is my setup.py test file content:
from distutils.core import setup
setup(name='foo', version='1.0', packages=['tes
Changes by Jan-Philip Gehrcke :
Added file: http://bugs.python.org/file38006/issue18454_py27_prompt_test.patch
___
Python tracker
<http://bugs.python.org/issue18
New submission from Jan-Philip Gehrcke:
When Python is invoked with the `-c command` switch, the command string does
not get exposed in sys.argv:
$ python -c "import sys; print(sys.argv)"
['-c']
$ python -c "import sys; print(sys.argv)" arg1
[
Jan-Philip Gehrcke added the comment:
I'd love to find an agreement here. I think we are quite close to getting this
closed, so further input is very welcome.
--
___
Python tracker
<http://bugs.python.org/i
Jan-Philip Gehrcke added the comment:
Can these super-small doc patches get applied or should we change something?
Thanks!
--
___
Python tracker
<http://bugs.python.org/issue20
Jan-Philip Gehrcke added the comment:
Victor,
I support the idea of sys.command. However, it would be unpopulated most of the
time (e.g. set to None by default). Now, is that something we should push
forward or not? I would work on a patch, but we should have an agreement first,
I guess
Jan-Philip Gehrcke added the comment:
Martin, I very much like the order you suggested, thanks. I did not feel
confident enough for re-structuring the entire entry. So, can we agree on using
that for Python 2.7?
Is there a consensus regarding the approach to take for Python 3.5? Except from
Changes by Jan-Philip Gehrcke :
Added file: http://bugs.python.org/file38096/issue6634_py27.patch
___
Python tracker
<http://bugs.python.org/issue6634>
___
___
Python-bug
Jan-Philip Gehrcke added the comment:
Thanks Christian, much appreciated. Just responded to your review.
--
___
Python tracker
<http://bugs.python.org/issue16
Jan-Philip Gehrcke added the comment:
Christian, Senthil, would appreciate if I got another round of feedback (in the
review thread) :-)
--
nosy: +orsenthil
___
Python tracker
<http://bugs.python.org/issue16
201 - 225 of 225 matches
Mail list logo