Change by Yves Duprat :
--
nosy: +yduprat
___
Python tracker
<https://bugs.python.org/issue46752>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Yves Duprat :
--
nosy: +yduprat
___
Python tracker
<https://bugs.python.org/issue46771>
___
___
Python-bugs-list mailing list
Unsubscribe:
Yves Duprat added the comment:
This last version includes the propositions, remarks from @asveltov and @eamanu
This PR is always stuck, so could you please approve the 3 running workflows ?
--
status: pending -> open
___
Python tracker
<
Yves Duprat added the comment:
An update was submitted on PR.
Modified python files are:
file lib/asyncio/locks.py
file lib/test/test_asyncio/test_locks.py
And related documentation files
file Doc/library/asyncio-api-index.rst
file Doc/library/asyncio-sync.rst
Please, could
New submission from Yves Duprat :
Add a synchronized primitive Barrier in asyncio, in order to be consistent with
them we have for threading.
Barrier object will have a similar design from that of threading lib.
(May be we have to think about a backport ?)
Initial discussion started here
New submission from Yves :
On different platforms and versions the following expression has different
results:
python -c 'import re; print(re.compile("(.*)", 0).sub("a\\1", "bc"))'
As far is I observed:
Linux/Python 3.6.9 => abc
MacOS/Py
New submission from Pier-Yves Lessard:
PF_CAN socket using ISO-TP protocol cannot be used as getsockaddrarg only
supports CAN_RAW and CAN_BCM for AF_CAN addresses.
--
components: Library (Lib)
messages: 298832
nosy: Pier-Yves Lessard
priority: normal
severity: normal
status: open
title
New submission from Yves Müller:
I am trying to read json containing a UTF-8 string from a file. It works when
running it from a shell with LANG=en_GB.utf8 set, but fails from the empty
environment.
> python3 --version
Python 3.4.0
> cat test.json
{ "test": "Ümläute&quo
New submission from Yves Dorfsman :
The basic time format in the logging module uses a comma instead of a dot to
separate the seconds from the tenth of seconds:
import logging
logging.basicConfig(format='%(asctime)s %(message)s')
logging.warning('hello')
201
Yves Dorfsman added the comment:
Added a test case:
http://hg.zioup.org/cpython/rev/4accd3181061
If you set the loop < 128 then the test passes (set at 1000 right now).
--
hgrepos: +65
___
Python tracker
<http://bugs.python.org/issu
New submission from Yves Dorfsman :
html.parser.HTMLParser.unescape works only with the first 128 entities, it
leaves the other ones as they are.
--
components: None
messages: 143434
nosy: y...@zioup.com
priority: normal
severity: normal
status: open
title
Yves Dorfsman added the comment:
encoders.py:
Fixes the issue of base64'ed being > 76 chars
test_email.py:
-test that base64'ed binary is split into 76 chars lines
-WARRNING: Changes the test for MIMEApplication.test_body:
-it changes the name of the variable 'by
Changes by Yves Dorfsman :
Removed file: http://bugs.python.org/file20743/issue9298.patch
___
Python tracker
<http://bugs.python.org/issue9298>
___
___
Python-bugs-list m
Changes by Yves Dorfsman :
Removed file: http://bugs.python.org/file20742/issue9298-test.py
___
Python tracker
<http://bugs.python.org/issue9298>
___
___
Python-bug
Yves Dorfsman added the comment:
I've got two issues with this code (Lib/email/test/test_email.py):
1128 def test_body(self):
1129 eq = self.assertEqual
1130 bytes = b'\xfa\xfb\xfc\xfd\xfe\xff'
1131 msg = MIMEApplication(bytes)
1132 eq(
Yves Dorfsman added the comment:
I will. Please don't use my patch yet, it breaks something else in the
test_email:
./python Lib/test/regrtest.py test_email
[1/1] test_email
test test_email failed -- Traceback (most recent call last):
File "/export/incoming/python/py3k/Lib/
Yves Dorfsman added the comment:
Replaces b64encode by encodebytes.
--
keywords: +patch
Added file: http://bugs.python.org/file20743/issue9298.patch
___
Python tracker
<http://bugs.python.org/issue9
Yves Dorfsman added the comment:
Test if email.encoders.encode_base64 returns a single line string, or a string
broken up in 76 chars line, as per RFC.
--
Added file: http://bugs.python.org/file20742/issue9298-test.py
___
Python tracker
<h
Yves Dorfsman added the comment:
#!/usr/bin/python3.1
import unittest
import email.mime.image
class emailEncoderTestCase(unittest.TestCase):
def setUp(self):
# point to an image
binaryfile = ''
#binaryfile =
'/usr/share/openclipart/png/
Yves Dorfsman added the comment:
Here's a better version (sorry I don't know how to remove msg128255:
--
___
Python tracker
<http://bugs.python.
Yves Dorfsman added the comment:
#!/usr/bin/python3.1
import unittest
import email.mime.image
class emailEncoderTestCase(unittest.TestCase):
def setUp(self):
# point to an image
binaryfile =
'/usr/share/openclipart/png/animals/mammals/happy_monkey_benji_park_01.png'
Yves Dorfsman added the comment:
Solution:
In /usr/lib/python3.1/email/encoders.py, use encodebytes instead of b64encode:
--- encoders.py 2011-02-08 09:37:21.025030051 -0700
+++ encoders.py.yves2011-02-08 09:38:04.945608365 -0700
@@ -12,7 +12,7 @@
]
-from base64 import b64encode
Yves Dorfsman added the comment:
In case this does not get fixed for a long time, here is a work around
(re-implement the encoder yourself):
.
.
.
def myencoder(msg):
from base64 import encodebytes as _bencode
orig = msg.get_payload()
encdata = str(_bencode(orig), '
New submission from Yves Dorfsman :
email.encoders.encode_base64 returns a str of a single long line instead of
breaking it up into 76 chars line as per RFC 2045, and as implemented by
email.base64mime.
Solution:
In /usr/lib/python3.1/email/encoders.py, use encodebytes instead of b64encode
Jean-Yves MENGANT added the comment:
Let me provide my contribution to this discussion around this ZOS port
topic :
I initially made the Python 2.2 and 2.4 for ZOS platform and ask the
python community to link to my pages as a support to ZOS at that time
Lauri get in touch with me couple of
25 matches
Mail list logo
