Hans-Peter Jansen added the comment:
If I'm not mistaken, this is applied to the openSUSE TW version of Python.
For some reason, this seems to not play well with .uid('move',...)
on a cyrus imap server (v2.4.19). Is that to be expected?
```
2020-07-03 18:04:05 INFO: [imap_reorg] move b
Changes by Hans-Peter Jansen <h...@urpla.net>:
--
nosy: +frispete
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue9253>
___
__
New submission from Hans-Peter Jansen:
In an attempt of using ctypes.from_buffer() to map a structure to a memory
mapped file, it is important to destroy the mapping after use, because the mmap
won't be resizable or freeable correctly until then.
The best approach, I was able to came up
Hans-Peter Jansen added the comment:
> (In msg271688, I pondered if I need to backport a behavior change from
> issue26804 which will allow lower cased proxies, but then, I decided against
> it as it will introduce unnecessary changes to this security fix releases).
Hmm, Senthil
Hans-Peter Jansen added the comment:
message.get cannot decode the header correctly, and returns a Header instance
instead, which makes email.utils.getaddresses stumble upon...
A much better behavior for getaddresses in this case would be returning the
perfectly valid address, and ignoring
New submission from Hans-Peter Jansen:
An unfortunate combination of get_all and getaddresses results in a Traceback:
Traceback (most recent call last):
File "misc/decode_from_header.py", line 17, in
print('From: %s' % email.utils.getaddresses(val))
File "/usr/lib64/
Hans-Peter Jansen added the comment:
Sorry guys for not providing this earlier.
It turned out, that the sub optimal behaviour is related to a unfortunate
policy choice: email.policy.SMTP.
--
Added file: http://bugs.python.org/file43417/email_flatten.py
Hans-Peter Jansen added the comment:
Sorry guys for not providing this earlier.
It turned out, that the sub optimal behaviour is related to a unfortunate
policy choice: email.policy.SMTP.
--
Added file: http://bugs.python.org/file43416/email_flatten.py
Hans-Peter Jansen added the comment:
Sorry guys for not providing this earlier.
It turned out, that the sub optimal behaviour is related to a unfortunate
policy choice: email.policy.SMTP.
--
Added file: http://bugs.python.org/file43415/email_flatten.py
Hans-Peter Jansen added the comment:
In a couple of systems, I have to stick with 3.4. Is there a chance to have
this patch in 3.4 as well, if a new release 3.4 is made?
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.p
Hans-Peter Jansen added the comment:
Dear Stephen,
thanks for your care. I'm glad, that you're able to reproduce it.
This header is added from the email provider (the biggest here in Germany), so
yes, it deserves an entry in the defects list, but must not traceback, of
course
New submission from Hans-Peter Jansen:
Attached mail, parsed with email.message_from_binary_file results in:
Traceback (most recent call last):
File "./mail_filter.py", line 616, in
ret = main.run()
File "./mail_filter.py", line 605, in run
self.process(fp)
Fi
New submission from Hans-Peter Jansen:
In the course of replacing an old Python 2.7 email filter tool with a rewritten
Python3 version, I stumbled across a ugly case, where such an header:
To: unlisted-recipients: ;,
""@pop.kundenserver.de (no To-header on input
Changes by Hans-Peter Jansen <h...@urpla.net>:
Added file: http://bugs.python.org/file43286/mf.9__mi0bf.out
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
New submission from Hans-Peter Jansen:
In the course of replacing an old Python 2.7 email filter tool with a rewritten
Python3 version, I stumbled across a ugly case, where such an header:
X-Microsoft-Exchange-Diagnostics:
=?utf-8?B?MTtCTDJQUjAyTUI1MTQ7MjM6bEtRRlNaUHQvVTk5WCttdktlOUVrUGQvVFBH
Hans-Peter Jansen added the comment:
Poor old bug.
Just being bitten from it today, while trying to package pyftpdlib on the
openSUSE build service, which creates a clean reproducible build environment
for all packages, and testing fails.
Part of the game: openssl 1.0.1k, Python 2.7.8
https
Hans-Peter Jansen added the comment:
v7:
- reorder test code in order to improve edibility
--
Added file:
http://bugs.python.org/file42586/python-urllib-prefer-lowercase-proxies-v7.diff
___
Python tracker <rep...@bugs.python.org>
Hans-Peter Jansen added the comment:
> In Python 2, it looks like the proxy_bypass_etc() functions are defined
> in urllib and imported into urllib2, so it makes sense to include the
> tests in test_urllib rather than test_urllib2.
The tests are in test_urllib. test_urllib2 is test
Hans-Peter Jansen added the comment:
* blatant error fixed
* one test case added
--
Added file:
http://bugs.python.org/file42582/python-urllib-prefer-lowercase-proxies-v6.diff
___
Python tracker <rep...@bugs.python.org>
<http://bugs.p
New submission from Hans-Peter Jansen:
ConfigParser fails in interesting ways, when using default_section and
ExtendedInterpolation options. Running the attached script results in:
ConfigParser() with expected result:
global: [('loglevel', 'WARNING'), ('logfile', '-')]
section1: [('key_a
Hans-Peter Jansen added the comment:
v5: don't require the proxies argument in proxy_bypass_environment()
--
Added file:
http://bugs.python.org/file42565/python-urllib-prefer-lowercase-proxies-v5.diff
___
Python tracker <rep...@bugs.python.
Hans-Peter Jansen added the comment:
Here's the finalized version of this patch, including unit tests.
--
Added file:
http://bugs.python.org/file42552/python-urllib-prefer-lowercase-proxies-v4.diff
___
Python tracker <rep...@bugs.python.org>
Hans-Peter Jansen added the comment:
Here we go:
v3 fixes following issues:
* prefer lowercase proxy environment settings, if multiple (disagreeing)
settings are specified with differing case schemes (e.g. HTTP_PROXY vs.
http_proxy)
* an empty proxy variable value resets the related setting
Hans-Peter Jansen added the comment:
Hi Martin, hi Senthil,
please find a new patch attached, that incorporates your suggestions.
* added a comment to get_proxies doc in urllib.rst
* documented and fixed the mixed case scheme
* added a note to proxy_bypass_environment, that behaves
Hans-Peter Jansen added the comment:
Hi Martin, hi Senthil,
thanks for the valuable comments.
Will incorporate your suggestions later today.
Yes, Martin, it's a bug, and should be fixed for 2.7 and 3.5 as well, but I was
unsure, if I get some feedback at all... Hence, this is a very nice
Changes by Hans-Peter Jansen <h...@urpla.net>:
--
versions: +Python 3.6 -Python 3.5
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
New submission from Hans-Peter Jansen:
During programming a function, that replaces a wget call, I noticed, that
something is wrong with urllibs proxy handling.
I usually use the scheme "http_proxy= wget -N -nd URL" when I need to bypass
the proxy. Hence I was prett
Hans-Peter Jansen [EMAIL PROTECTED] added the comment:
Facundo, first of all: *really* nice work, thanks a lot.
While I don't fully understand the issues raised lately here,
especially what broke (user code). I can see, that it completely
solves my original problem, which is great.
While
Hans-Peter Jansen [EMAIL PROTECTED] added the comment:
But should not this patch be handled in a way wherein.
key.capitalize() is just replaced by key.upper()?
Hmm, are you sure?
hello.upper()
'HELLO'
but the issue is with values containing dashes:
'accept-charset'.capitalize()
'Accept
Hans-Peter Jansen [EMAIL PROTECTED] added the comment:
Hi Senthil,
that looks promising, and the title() trick is nice, as it fixes my
issue..
Thanks,
Pete
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2275
New submission from Hans-Peter Jansen [EMAIL PROTECTED]:
The urllib2 behavior related to headers is - hmm - improvable.
It simply capitalize() the key, which leads to funny results like:
Accept-charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
while this is seemingly conforming to the specs, it's simply
31 matches
Mail list logo
