[issue1210] imaplib does not run under Python 3

Christian Heimes <[EMAIL PROTECTED]> added the comment: Committed in r67107 -- resolution: accepted -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue1210] imaplib does not run under Python 3

STINNER Victor <[EMAIL PROTECTED]> added the comment: Le Tuesday 04 November 2008 00:59:02 Barry A. Warsaw, vous avez écrit : > The assertion on line 813 is indented incorrectly. Please fix that. Ooops. I'm using the following command because my editor is configured to remove the trailing space

[issue1210] imaplib does not run under Python 3

Changes by Raghuram Devarakonda <[EMAIL PROTECTED]>: -- nosy: -draghuram ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-lis

[issue1210] imaplib does not run under Python 3

Changes by Jean-Paul Calderone <[EMAIL PROTECTED]>: -- nosy: -exarkun ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list m

[issue1210] imaplib does not run under Python 3

Changes by STINNER Victor <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file11796/imaplib_bytes-3.patch ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue1210] imaplib does not run under Python 3

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- assignee: -> benjamin.peterson nosy: +benjamin.peterson ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue1210] imaplib does not run under Python 3

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: The assertion on line 813 is indented incorrectly. Please fix that. I'm concerned we really need better test coverage for this code, but it's doubtful we'll get that before 3.0 final is released. I think this is the best we're going to do,

[issue1210] imaplib does not run under Python 3

STINNER Victor <[EMAIL PROTECTED]> added the comment: Can anyone review my last patch (imaplib_bytes-3.patch)? -- keywords: +needs review ___ Python tracker <[EMAIL PROTECTED]> ___

[issue1210] imaplib does not run under Python 3

STINNER Victor <[EMAIL PROTECTED]> added the comment: Oops, my previous patch didn't include changes to the documentation. New patch changes: - fix the documentation: os.popen2() => subprocess.Popen(); no more ssl() method: use socket() - use a buffer of 4096 bytes in read() method (as sugges

[issue1210] imaplib does not run under Python 3

Changes by STINNER Victor <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file11795/imaplib_bytes-2.patch ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue1210] imaplib does not run under Python 3

Changes by STINNER Victor <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file11794/imaplib_bytes.patch ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue1210] imaplib does not run under Python 3

STINNER Victor <[EMAIL PROTECTED]> added the comment: New version of my bytes patch: - fix IMAP4_stream: use subprocess.Popen() as my previous imap_stream.patch but use bytes instead of characters - fix IMAP4_SSL: sslobj wasn't set in IMAP4_SSL.open() but used, for example, in read() method;

[issue1210] imaplib does not run under Python 3

Changes by STINNER Victor <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file11792/imaplib_stream.patch ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue1210] imaplib does not run under Python 3

STINNER Victor <[EMAIL PROTECTED]> added the comment: The server can send raw 8 bits email in any charset (charset is specified in the email headers). That's why I think that it's better to keep bytes instead of the unicode conversion using a fixed charset. Each email can use a different chars

[issue1210] imaplib does not run under Python 3

Changes by STINNER Victor <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file11786/imaplib_unicode.patch ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue1210] imaplib does not run under Python 3

Bill Janssen <[EMAIL PROTECTED]> added the comment: Maybe the first thing to do is to expand the Lib/test/test_imaplib.py file, which right now is pretty darn minimal. We really need an IMAP server somewhere to test against, with a standard library of varied messages. Perhaps Python.org is runn

[issue1210] imaplib does not run under Python 3

STINNER Victor <[EMAIL PROTECTED]> added the comment: > what kind of content have you tried this with? I only tried the most basic commands like capability(). I retried with search() and... hey, search() has a charset argument!? It should reuse self.encoding. Same for sort(). Then I tried to

[issue1210] imaplib does not run under Python 3

STINNER Victor <[EMAIL PROTECTED]> added the comment: IMAP_stream() is also broken because it uses os.popen2() which has been deprecated since long time and now replaced by subprocess. Here is a patch replacing os.popen2() by subprocess, but also using transparent conversion from/to unicode us

[issue1210] imaplib does not run under Python 3

Changes by STINNER Victor <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file11790/unnamed ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue1210] imaplib does not run under Python 3

Bill Janssen <[EMAIL PROTECTED]> added the comment: Victor, what kind of content have you tried this with? For instance, have you passed unencoded (Content-Transfer-Encoding: binary) binary data through it, by mailing a JPEG, for instance? These things are strings really only at the application

[issue1210] imaplib does not run under Python 3

STINNER Victor <[EMAIL PROTECTED]> added the comment: Here is a patch for imaplib: - add encoding attribute to IMAP4 class (as ftplib and see also issue 3727 for my poplib patch) - use makefile('r', encoding=self.encoding) instead of a binary file (mode='rb') - remove duplicate code in IMAP4

[issue1210] imaplib does not run under Python 3

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: deferred blocker -> release blocker ___ Python tracker <[EMAIL PROTECTED]> ___

[issue1210] imaplib does not run under Python 3

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: release blocker -> deferred blocker ___ Python tracker <[EMAIL PROTECTED]> ___

[issue1210] imaplib does not run under Python 3

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: deferred blocker -> release blocker ___ Python tracker <[EMAIL PROTECTED]> ___

[issue1210] imaplib does not run under Python 3

Bill Janssen <[EMAIL PROTECTED]> added the comment: Take a look at the thread here: http://mailman2.u.washington.edu/mailman/htdig/imap-protocol/2008-February/000811.html I think the summary is, arbitrary bytes may occur in some places, but they're likely to be UTF-8. Otherwise, it's mainly AS

[issue1210] imaplib does not run under Python 3

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: This should be fixed but it's not a release blocker. -- nosy: +barry priority: release blocker -> deferred blocker ___ Python tracker <[EMAIL PROTECTED]> ___

[issue1210] imaplib does not run under Python 3

Neal Norwitz <[EMAIL PROTECTED]> added the comment: This may not be a real release blocker, but I want to raise the priority. It is a regression and we should try to fix it, especially if it's easy. -- priority: normal -> release blocker ___ Python t

[issue1210] imaplib does not run under Python 3

Ismail Donmez <[EMAIL PROTECTED]> added the comment: Still fails with beta2: >>> import imaplib >>> mail=imaplib.IMAP4("mail.rtmq.infosathse.com") Traceback (most recent call last): File "", line 1, in File "/usr/local/lib/python3.0/imaplib.py", line 185, in __init__ self.welcome = self

[issue1210] imaplib does not run under Python 3

Neal Norwitz <[EMAIL PROTECTED]> added the comment: Is this still a problem? -- nosy: +nnorwitz type: crash -> behavior ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue1210] imaplib does not run under Python 3

Bill Janssen added the comment: IMAP doesn't really support multiple charsets (just looked at RFC 3501). There are two places where character sets other than ASCII is used. One is in the SEARCH command; there's an optional parameter which can indicate that the search strings are in a non-ASCII

[issue1210] imaplib does not run under Python 3

Jean-Paul Calderone added the comment: You're correct in pointing out that IMAP4 supports arbitrary encodings, so simply hard-coding ASCII is not correct. The encoding isn't connection-level, but applies to particular sequences of bytes in the connection stream. To correctly interpret the bytes

[issue1210] imaplib does not run under Python 3

Raghuram Devarakonda added the comment: Index: Lib/imaplib.py === --- Lib/imaplib.py (revision 58956) +++ Lib/imaplib.py (working copy) @@ -228,7 +228,7 @@ self.port = port self.sock = socket.socket(socket

[issue1210] imaplib does not run under Python 3

Raghuram Devarakonda added the comment: I will see what I can do but it may take a while. __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing

[issue1210] imaplib does not run under Python 3

Christian Heimes added the comment: The transition is done. Can you work on a patch and maybe add some tests, too? It helps when you start Python with the -bb flag: $ ./python -bb -c 'import imaplib; imaplib.Debug=5; imaplib.IMAP4("mail.rtmq.infosathse.com")' 52:01.86 imaplib version 2.58 52

[issue1210] imaplib does not run under Python 3

Changes by Christian Heimes: -- keywords: +py3k priority: -> normal resolution: -> accepted __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-

[issue1210] imaplib does not run under Python 3

Raghuram Devarakonda added the comment: I have gone through the python-3000 discussions about similar problems in other stdlib modules (email, imghdr, sndhdr etc) and found PEP 3137 (Immutable Bytes and Mutable Buffer). Since that work is in progress, I don't think it is worthwhile to fix this pr

[issue1210] imaplib does not run under Python 3

Raghuram Devarakonda added the comment: Just to further understand the issue, I added "imaplib.Debug=5" and here is the output preceding the exception stack trace(I replaced the real IMAP server name) *** 20:19.52 imaplib version 2.58 20:19.52 new IMAP4 connection, tag=LOLD 20:

[issue1210] imaplib does not run under Python 3

Changes by Raghuram Devarakonda: -- nosy: +draghuram __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue1210] imaplib does not run under Python 3

Martin v. Löwis added the comment: Would you like to work on a patch? -- nosy: +loewis __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list ma

[issue1210] imaplib does not run under Python 3

New submission from Robert T McQuaid: imaplib does not run under Python 3. The following two-line python program, named testimap.py, works when run from a Windows XP system shell prompt using Python 2.5.1, but fails with Python 3.0. It appears that the logic does not follow the distinction betw