New submission from Jonathan Gossage :
I installed Python 3.8.0b4 manually on Ubuntu 19.04 desktop. After the
installation that appeared to run OK, I was unable to find python3.8, even
though it had been installed in /usr/local/bin and that directory was on the
path. I got the result
Jonathan Gossage added the comment:
I now do not think that it is a Python problem. It only appears when Ubuntu
18.04 is upgraded to 19.04 by the upgrade process. The problem does not
show up on a fresh install of Ubuntu 19.04 followed by a source install of
Python 3.8.0b4 only if the install
New submission from Jonathan Gossage :
Python 3.8 was installed from source on Ubuntu 19.04 desktop and a virtual
environment was created with python3.8 -m venv venvrh. When attempting to use
pip to install a package, the following error was encountered:
(venvrh) jgossage@jgossage-XPS-8700
Jonathan Gossage added the comment:
This is a great example of abusing the multi-processing API and thus
creating timing errors that lead to locks not being released. What is
happening is that the example attempts to transmit data that is too
big for the underlying pipe and this creates the
Change by Jonathan Gossage :
Added file: https://bugs.python.org/file47980/lock1.result.txt
___
Python tracker
<https://bugs.python.org/issue35267>
___
___
Python-bug
Jonathan Gossage added the comment:
I think documentation is sufficient but I would like it to state the pitfalls
available if apply_async is not synchronized correctly which will happen
whenever the output does not fit the pipe buffer
Change by Jonathan Gossage :
--
pull_requests: +9101
stage: test needed -> patch review
___
Python tracker
<https://bugs.python.org/issue6686>
___
___
Python-
Jonathan Gossage added the comment:
The other thing to consider which also supports option 2 is that
xml.parsers.expat provides an interface to the Expat parser which is easier to
use and more complete than the Sax parser implementation and is the
implementation likely to be used by anyone
Jonathan Gossage added the comment:
This test case demonstrates that the issue still exists in 3.8. The fix is
relatively simple but I am unsure whether it is worthwhile as the original
comments on the quality and usability of SAX2DOM are spot on. My recommendation
would be to mark it as
Change by Jonathan Gossage :
--
keywords: +patch
pull_requests: +9272
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue9453>
___
___
Py
New submission from Jonathan Gossage :
While working on issues bpo-6686 and bpo-9371 I realized that the solution to
both involved the use of Sax lexical handlers. Unfortunately, the Python SAX
parser does not expose these handlers to the end user, however, support is
available in
Change by Jonathan Gossage :
--
components: +XML
___
Python tracker
<https://bugs.python.org/issue35018>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Jonathan Gossage :
--
pull_requests: +9632
___
Python tracker
<https://bugs.python.org/issue6686>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Jonathan Gossage :
--
keywords: +patch
pull_requests: +9631
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue35018>
___
_
Change by Jonathan Gossage :
--
pull_requests: +9633
___
Python tracker
<https://bugs.python.org/issue9731>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Jonathan Gossage :
--
pull_requests: +9635
___
Python tracker
<https://bugs.python.org/issue9371>
___
___
Python-bugs-list mailing list
Unsubscribe:
16 matches
Mail list logo