Re: [Email-SIG] Some parsing/generation issues of email in Python 3

2016-06-12 Thread Matthew Dixon Cowles
Pete, Here's another thought for whatever it's worth: Do you get the same result if you make your own copy of the logging module? If you do, can you, er, log from it to see just what it's doing? Regards, Matt ___ Email-SIG mailing list Email-SIG@python.

Re: [Email-SIG] Some parsing/generation issues of email in Python 3

2016-06-12 Thread Hans-Peter Jansen
Hi Matt, thanks for your hints. On Sonntag, 12. Juni 2016 13:01:13 Matthew Dixon Cowles wrote: > Pete, > > > Note, that the subject line is missing. In my real filter, it left > > the current execution frame, and execution continued one or two > > level up the stack. > > The only thing I've run

Re: [Email-SIG] Some parsing/generation issues of email in Python 3

2016-06-12 Thread Matthew Dixon Cowles
Pete, > Note, that the subject line is missing. In my real filter, it left > the current execution frame, and execution continued one or two > level up the stack. The only thing I've run into that's like that is when an exception is raised in a function that I didn't think would do that and was c

Re: [Email-SIG] Some parsing/generation issues of email in Python 3

2016-06-12 Thread Hans-Peter Jansen
[This mail is intentionally hand wrapped..] On Freitag, 10. Juni 2016 17:54:34 Hans-Peter Jansen wrote: > On Donnerstag, 9. Juni 2016 18:37:54 Hans-Peter Jansen wrote: > > > > Let's see, how this goes. > > Hmm, compat32 and Python3 start to get in my way in no funny ways. Okay, got it working n

Re: [Email-SIG] Some parsing/generation issues of email in Python 3

2016-06-10 Thread Hans-Peter Jansen
On Donnerstag, 9. Juni 2016 18:37:54 Hans-Peter Jansen wrote: > On Mittwoch, 8. Juni 2016 10:37:41 R. David Murray wrote: > > Right, in my previous note I was talking about people not using the > > new policies. The compat32 code is probably being used by a lot of > > people and seems to be workin

Re: [Email-SIG] Some parsing/generation issues of email in Python 3

2016-06-09 Thread R. David Murray
On Thu, 09 Jun 2016 18:37:54 +0200, Hans-Peter Jansen wrote: > Apart from all considerations related to streaming/memory > consumption/assembly, IMHO the weakest spot of the email package is header > handling: the magic formula > > str(email.header.make_header(email.header.decode_header(msg['

Re: [Email-SIG] Some parsing/generation issues of email in Python 3

2016-06-09 Thread Hans-Peter Jansen
On Mittwoch, 8. Juni 2016 10:37:41 R. David Murray wrote: > > Right, in my previous note I was talking about people not using the > new policies. The compat32 code is probably being used by a lot of > people and seems to be working well, including having fixed some header > parsing and folding bu

Re: [Email-SIG] Some parsing/generation issues of email in Python 3

2016-06-08 Thread R. David Murray
On Wed, 08 Jun 2016 23:04:46 +0200, Hans-Peter Jansen wrote: > Usually, when I report such problems nowadays, I add a patch proposal for > fixing the issue, but these issues were overwhelming me. Needless to mention > the complexity of the email package itself and my reluctance of studying RFCs.

Re: [Email-SIG] Some parsing/generation issues of email in Python 3

2016-06-08 Thread Hans-Peter Jansen
[Sorry Stephen, wrong key...] On Mittwoch, 8. Juni 2016 23:42:31 you wrote: > Hans-Peter Jansen writes: > > Dear audience, > > > > when coming back to this list, I couldn't believe my eyes because > > of the low volume level, but after rechecking with the archives, I > > have to accept, it i

Re: [Email-SIG] Some parsing/generation issues of email in Python 3

2016-06-08 Thread Hans-Peter Jansen
On Mittwoch, 8. Juni 2016 10:14:16 Barry Warsaw wrote: > On Jun 08, 2016, at 11:56 AM, Hans-Peter Jansen wrote: > >All these issues were harvested in less than halve an hour. What really > >troubles me is the quietness around here in the light of this experience. > >Doesn't people use Python (3) ye

Re: [Email-SIG] Some parsing/generation issues of email in Python 3

2016-06-08 Thread R. David Murray
On Wed, 08 Jun 2016 23:42:31 +0900, "Stephen J. Turnbull" wrote: > It's a complete rewrite from first principles. It's more robust in > principle and more maintainable in practice, but faced with 100s of > millions of emails (aka "tsunami of sewage"), the robustness can't be > guaranteed. I'm w

[Email-SIG] Some parsing/generation issues of email in Python 3

2016-06-08 Thread Stephen J. Turnbull
Hans-Peter Jansen writes: > Dear audience, > > when coming back to this list, I couldn't believe my eyes because > of the low volume level, but after rechecking with the archives, I > have to accept, it is that quiet here, a bit too quiet from my > POV. Hmm. It's just that very few people (

Re: [Email-SIG] Some parsing/generation issues of email in Python 3

2016-06-08 Thread R. David Murray
On Wed, 08 Jun 2016 10:14:16 -0400, Barry Warsaw wrote: > On Jun 08, 2016, at 11:56 AM, Hans-Peter Jansen wrote: > > >All these issues were harvested in less than halve an hour. What really > >troubles me is the quietness around here in the light of this experience. > >Doesn't people use Python

Re: [Email-SIG] Some parsing/generation issues of email in Python 3

2016-06-08 Thread Barry Warsaw
On Jun 08, 2016, at 11:56 AM, Hans-Peter Jansen wrote: >All these issues were harvested in less than halve an hour. What really >troubles me is the quietness around here in the light of this experience. >Doesn't people use Python (3) yet/anymore for these kind of tasks? Does >somebody care? Am

Re: [Email-SIG] Some parsing/generation issues of email in Python 3

2016-06-08 Thread R. David Murray
On Wed, 08 Jun 2016 11:56:40 +0200, Hans-Peter Jansen wrote: > All these issues were harvested in less than halve an hour. What really > troubles me is the quietness around here in the light of this experience. > Doesn't people use Python (3) yet/anymore for these kind of tasks? Does Apparentl

[Email-SIG] Some parsing/generation issues of email in Python 3

2016-06-08 Thread Hans-Peter Jansen
Dear audience, when coming back to this list, I couldn't believe my eyes because of the low volume level, but after rechecking with the archives, I have to accept, it is that quiet here, a bit too quiet from my POV. Hmm. Well, I'm in the course of replacing a special purpose postfix email filte