On Fri, Oct 10, 2014 at 3:05 PM, Glenn Linderman wrote:
> There are still lots of idiotic web sites that assume everything in front of
> the @ must be a letter, digit, dot, or hyphen, and even some that only
> permit one dot after the @... even though for 30 years or so, the RFCs have
> permitted
On 10/9/2014 7:41 PM, R. David Murray wrote:
Specifically, it is about what we might better term mailbox
*folders*...that is, not what you would normally think of as the
'mailbox name', which is usually understood to be the thing before the @
in the email address (and can't contain non-ASCII yet.
On Fri, 10 Oct 2014 13:36:49 +1100
Chris Angelico wrote:
> On Fri, Oct 10, 2014 at 11:52 AM, Jesus Cea wrote:
> > Actually, it doesn't work in Python 2 either. It never supported
> > international mailbox names.
> >
> > Should I dare to suggest to port this to 2.7, since 2.7 is special and
> > wi
On Fri, 10 Oct 2014 04:28:21 +0200, Antoine Pitrou wrote:
> On Thu, 9 Oct 2014 19:12:29 -0700
> Dan Stromberg wrote:
> > On Thu, Oct 9, 2014 at 3:47 PM, Jesus Cea wrote:
> > > I miss mUTF-7 support (as used to encode IMAP4 mailbox names) in Python,
> > > in the codecs module. As an european with
On Fri, Oct 10, 2014 at 11:52 AM, Jesus Cea wrote:
> Actually, it doesn't work in Python 2 either. It never supported
> international mailbox names.
>
> Should I dare to suggest to port this to 2.7, since 2.7 is special and
> will be supported for a long time?. Or maybe this is something like
> "Y
On Thu, 9 Oct 2014 19:12:29 -0700
Dan Stromberg wrote:
> On Thu, Oct 9, 2014 at 3:47 PM, Jesus Cea wrote:
> > I miss mUTF-7 support (as used to encode IMAP4 mailbox names) in Python,
> > in the codecs module. As an european with a language with 27 different
> > letters (instead of english 26), ti
On Thu, Oct 9, 2014 at 3:47 PM, Jesus Cea wrote:
> I miss mUTF-7 support (as used to encode IMAP4 mailbox names) in Python,
> in the codecs module. As an european with a language with 27 different
> letters (instead of english 26), tildes, opening question marks, etc., I
> find it very inconvenien
2014-10-10 2:52 GMT+02:00 Jesus Cea :
> "Yes, Python 2 is broken, the real deal is Python 3"? :).
For Unicode, my favorite answer is "it's time to upgrade! Python 3 has
a much better Unicode support." and not fix the issue on Python 2.7.
I don't want to open the can of worm "unicode" in Python 2.
On Fri, Oct 10, 2014 at 1:29 AM, Victor Stinner
wrote:
> Hi,
>
> Windows is not the primary target of Python developers, probably
> because most of them work on Linux. Official Python binaries are
> currently built by Microsoft Visual Studio. Even if Python developers
> get free licenses thanks fo
On 10/10/14 02:43, Victor Stinner wrote:
> 2014-10-10 2:34 GMT+02:00 Jesus Cea :
>>> What is the current behaviour of imaplib in Python 3.4 with non-ASCII
>>> characters in mailbox names?
>>
>> It breaks. Crash & burn.
>
> Oh ok. So in short, imaplib doesn't work on Python 3: it's a bug and
> it m
2014-10-10 2:34 GMT+02:00 Jesus Cea :
>> What is the current behaviour of imaplib in Python 3.4 with non-ASCII
>> characters in mailbox names?
>
> It breaks. Crash & burn.
Oh ok. So in short, imaplib doesn't work on Python 3: it's a bug and
it must be fixed. I agree that a new codec is good idea a
On 10/10/14 02:00, Victor Stinner wrote:
> 2014-10-10 1:33 GMT+02:00 Jesus Cea :
>> The purpose of these modifications is to correct the following
>>problems with UTF-7:
>
> If you need performances, I would be interested to see if it would be
> possible to reuse the C codec for UTF-7 to share
On Fri, 10 Oct 2014 01:33:58 +0200, Jesus Cea wrote:
> On 10/10/14 01:08, Victor Stinner wrote:
> > When you say "IMAP4", do you mean any IMAP4 server? Do you have a list
> > of server vendors known to use the encoding mUTF-7?
>
> All of them. IMAP4 protocol **REQUIRES** mUTF-7.
[...]
> I am vo
Hi,
Windows is not the primary target of Python developers, probably
because most of them work on Linux. Official Python binaries are
currently built by Microsoft Visual Studio. Even if Python developers
get free licenses thanks for Microsoft, I would prefer to use an open
source compiler if it wo
2014-10-10 1:33 GMT+02:00 Jesus Cea :
> The purpose of these modifications is to correct the following
>problems with UTF-7:
If you need performances, I would be interested to see if it would be
possible to reuse the C codec for UTF-7 to share as much code as
possible.
What is the current beh
On 10/09/2014 03:47 PM, Jesus Cea wrote:
[] mUTF-7 support [...]
What do you think?. Could be considered for Python 3.5?.
+1
--
~Ethan~
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsub
On 10/10/14 01:08, Victor Stinner wrote:
> When you say "IMAP4", do you mean any IMAP4 server? Do you have a list
> of server vendors known to use the encoding mUTF-7?
All of them. IMAP4 protocol **REQUIRES** mUTF-7.
UTF-8 is optional in IMAP4, and even UTF-8 capable servers have to
support clien
On Fri, 10 Oct 2014 00:47:46 +0200
Jesus Cea wrote:
> I miss mUTF-7 support (as used to encode IMAP4 mailbox names) in Python,
> in the codecs module. As an european with a language with 27 different
> letters (instead of english 26), tildes, opening question marks, etc., I
> find it very inconven
Hi,
You can develop a codec and plug it into Python 3.4 right now using
codecs.register().
It's difficult to decide if a codec is important enough to be added to Python.
When you say "IMAP4", do you mean any IMAP4 server? Do you have a list
of server vendors known to use the encoding mUTF-7? Is
I miss mUTF-7 support (as used to encode IMAP4 mailbox names) in Python,
in the codecs module. As an european with a language with 27 different
letters (instead of english 26), tildes, opening question marks, etc., I
find it very inconvenient.
This encoding is used basically only in IMAP4, I know.
20 matches
Mail list logo
