[issue1874] email parser does not register a defect for invalid Content-Transfer-Encoding on multipart messages

Sergio Oliveira Campos <[EMAIL PROTECTED]> added the comment: Added check to conform RFC2045 (section 6.4) for Python 2.6 -- nosy: +seocam Added file: http://bugs.python.org/file10275/issue1874-fixed-2.6.patch __ Tracker <[EMAIL PROTECTED]>

[issue1874] email parser does not register a defect for invalid Content-Transfer-Encoding on multipart messages

Changes by Vinicius Baggio Fuentes <[EMAIL PROTECTED]>: -- nosy: +vinibaggio __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list

[issue1491] BaseHTTPServer incorrectly implements response code 100

samwyse <[EMAIL PROTECTED]> added the comment: Although any given implementation of an HTTP server is likely to serve up its headers in a predicable, repeatable, order, I don't think that we should specify a particular order in the test suite. Section 4.2 of RFC 2616 specifically states, "The or

[issue2814] Remove old classes from mailbox module

New submission from Humberto Diogenes <[EMAIL PROTECTED]>: mailbox.py has one section marked as "classes from the original module (for backward compatibility)", which are all listed as deprecated in the module documentation. In issue 756982, A. M. Kuchling agreed that "removing those old class

[issue2814] Remove old classes from mailbox module

Changes by Humberto Diogenes <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file10277/mailbox-remove_deprecated_doc.patch __ Tracker <[EMAIL PROTECTED]> __ ___

[issue1491] BaseHTTPServer incorrectly implements response code 100

samwyse <[EMAIL PROTECTED]> added the comment: In the attached file, I've refactored the entire BaseHTTPRequestHandlerTestCase class. In doing so, I couldn't help but notice that we're expecting HTTP/1.1 responses when sending HTTP/1.0 requests. RFC 2616 is unclear about whether this is legitim

[issue756982] mailbox should use email not rfc822

Humberto Diogenes <[EMAIL PROTECTED]> added the comment: I created issue 2814 with a patch to remove those old classes. Tracker <[EMAIL PROTECTED]> _

[issue2775] Implement PEP 3108

Brett Cannon <[EMAIL PROTECTED]> added the comment: Just so people know, I have emailed python-dev about renaming urllib as I realized there are some issues with the solution proposed in the PEP. -- priority: critical -> release blocker __ Tracker <[EMAI

[issue2815] Python Manuals: horizontal scrolling broken

New submission from Terry J. Reedy <[EMAIL PROTECTED]>: 3.0a5, Windows, Python Manuals window opened from Start menu Ordinary text wraps and adjusts to window width. Text in green boxes does not. If too long to fit window, given the font size, horizontal scroll bar at bottom gives access to over

[issue2736] datetime needs and "epoch" method

Miki Tebeka <[EMAIL PROTECTED]> added the comment: I think the name is not good, should be "toepoch" or something like that. __ Tracker <[EMAIL PROTECTED]> __ __

[issue2775] Implement PEP 3108

Andrews Patrick Rocha Medina <[EMAIL PROTECTED]> added the comment: The files Python/compile.c and Python/pythonrun.c depends of the _symtable (Python/symtable.c and Include/symtable.h). What I do for remove _symtable in py3k? __ Tracker <[EMAIL PROTECTED]>

[issue2775] Implement PEP 3108

Humberto Diogenes <[EMAIL PROTECTED]> added the comment: Andrews, this discussion would be more appropriate to the mailing list, but anyway: I believe you're mixing things up. When PEP 3108 says "remove symtable/_symtable", it must be talking only about symtable.py and symtablemodule.c, not sy

[issue1267629] pdb: implement "until",fix for 1248119

Georg Brandl <[EMAIL PROTECTED]> added the comment: Benjamin: please reformat to PEP 8, then this is okay to check in. Don't forget docs and NEWS updates. -- assignee: -> benjamin.peterson nosy: +benjamin.peterson, georg.brandl resolution: -> accepted _

<    1   2