Nikolaus Rath Nikolaus at rath.org
Wed Mar 26 05:37:16 CET 2014

• Previous message: [Python-Dev] SSLSocket.send() for non-blocking sockets
• Next message: [Python-Dev] C code: %s vs %U
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

Chris Angelico <rosuav at gmail.com> writes:
> On Wed, Mar 26, 2014 at 11:54 AM, Nikolaus Rath <Nikolaus at rath.org> wrote:
>> 2. Change the behavior immediately, potentially breaking some
>>    applications that worked around it, but unbreaking others that relied
>>    on the documented behavior.
>
> If it's a functionality change that's likely to break code, would it
> be worth changing it only in 3.5, and documenting it as broken in 3.4
> and earlier?

Yes, that's what I meant. I don't think changing it in 3.4 is an option
at all.


Best,
-Nikolaus

-- 
Encrypted emails preferred.
PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6  02CF A9AD B7F8 AE4E 425C

             »Time flies like an arrow, fruit flies like a Banana.«

---

• Previous message: [Python-Dev] SSLSocket.send() for non-blocking sockets
• Next message: [Python-Dev] C code: %s vs %U
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list