Sye van der Veen added the comment:
In the sep!=None case, there are existing alternatives to prune=True that
aren't many more keystrokes:
>>> ''.split(' ', prune=True)
[]
>>> [x for x in ''.split(' ') if x]
[]
>>>
Sye van der Veen added the comment:
I would also agree that failing to load the main codec should be an abort.
This bug was specifically the race condition in writing the .pyc file.
Thanks for all your help!
--
___
Python tracker
<h
Changes by Sye van der Veen :
--
nosy: +syeberman
___
Python tracker
<http://bugs.python.org/issue28005>
___
___
Python-bugs-list mailing list
Unsubscribe:
Sye van der Veen added the comment:
Consider a process that is terminated while writing a large .pyc file.
Currently a user can only fix this by deleting the .pyc file, which requires
knowing where to look. A developer can be expected to know this, but the end
user of their application
Sye van der Veen added the comment:
I feel this patch (file44424) misses the mark. Any two Python processes
that try to import a module, without a pyc, at the same time could suffer
race conditions. The first process will start to write the pyc, get
interrupted, and the second will fail with an
Sye van der Veen added the comment:
Signed and confirmed. :-)
On Thu, Nov 12, 2015 at 11:28 PM Martin Panter
wrote:
>
> Martin Panter added the comment:
>
> Sye van der Veen: can you sign a contributor agreement <
> https://www.python.org/psf/contrib/contrib-form/>
Changes by Sye van der Veen :
--
keywords: +patch
Added file: http://bugs.python.org/file31769/75843d82f6cf.diff
___
Python tracker
<http://bugs.python.org/issue19
New submission from Sye van der Veen:
In the ctypes documentation, there's mention of a
BigEndianUnion/LittleEndianUnion that isn't actually implemented, and the
"Arrays and pointers" section just reads "Not yet written".
The attached patch adds the (Big|Little)E
New submission from Sye van der Veen:
I'm working with Python's test suite and noticed this error:
http://hg.python.org/cpython/file/668aba845fb2/Lib/test/test_set.py#l1669
# etc...
for g in (G, I, Ig, L, R):
expected = meth(data)
actual = meth(G(data))
# etc...
I b
New submission from Sye van der Veen:
The PyMarshal_Read* functions raise EOFError when the end of the file is
unexpectedly met. The current import.c functions propagate this error when
reading .pyc or .pyo files. One consequence of this is that Python will abort
on startup if, say
Sye van der Veen added the comment:
This issue _does_ exist on Windows, and is not limited to the case where the
master process exits before its children. The following code, which is almost
exactly that from the 2.7.3 documentation, deadlocks on Win7 (Py3.2 and 2.7)
and WinXP (Py3.2 and
Sye van der Veen added the comment:
When I built the documentation on Win7, it failed with a SyntaxError, and it
took some digging to find the reason why. I was hoping that issuing this
warning would save others the trouble.
I agree: on Windows, PYTHON is rarely set. However, look in
New submission from Sye van der Veen :
I'm wanting to call PyThreadState_SetAsyncExc from a function registered with
SetConsoleCtrlHandler. To do so, I need to call PyGILState_Ensure, which
asserts that Python is initialized, so I need to check for that. However, I
noticed a race cond
Sye van der Veen added the comment:
I had trouble wording that sentence. Under Unix, Makefile is used, in which
you specify "PYTHON=" on the command line else the default "python" (from
the PATH) is used. Under Windows, it's make.bat, where PYTHON needs to be set
Sye van der Veen added the comment:
I ran smack into this while setting up my Doc build for the first time. In
trying to fix my build problems, it took me about an hour to find that this was
a known issue.
I've attached a patch to warn others of the issue, in the documentation an
Sye van der Veen added the comment:
I've attached a patch to remove "a replacement is expected for Python
2.5".
--
keywords: +patch
nosy: +syeberman
status: pending -> open
Added file: http://bugs.python.org/file14715/Issue812750.diff
16 matches
Mail list logo