Re: [Python-Dev] Asking for feedback about fixing `ftplib' (issue25458)
>From what I understand the problem should be fixed in urllib so that it always closes the FTP connection. I understand this is what happens in recent 3.x versions but not on 2.7. As for ftplib, I don't like the solution of using a `transfer_in_progress` flag in all commands. I see that as a cheap way to work around the fact that the user may forget to call voidresp() and close the socket after nt/transfercmd(). It probably makes sense to just update nt/transfercmd() doc instead and make that clear. On Mon, Dec 19, 2016 at 12:01 PM, Ivan Pozdeev via Python-Dev < [email protected]> wrote: > I'm currently working on http://bugs.python.org/issue25458 . > There are a few options there, and each one has drawbacks. > So, I'd like to get some feedback on which way is prefereable before > working towards any of them and/or other ideas should they arise. > > The problem and the options are summarized in > http://bugs.python.org/issue25458#msg283073 and the message after that > one. > > Apart from the options, I'd like to know if I must solve the 2nd problem > (error handling), too, or it can be handled in a separate ticket. > > -- > Regards, > Ivan > ___ > Python-Dev mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: https://mail.python.org/mailman/options/python-dev/g.rodola% > 40gmail.com > -- Giampaolo - http://grodola.blogspot.com ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] --with-fpectl changes the CPython ABI
On 25 December 2016 at 09:48, Nathaniel Smith wrote: > Or maybe make it so that even no-fpectl builds still export the > necessary symbols so that yes-fpectl extensions don't crash on import? > (This has the advantage that it can be done in a point release...) > This seems like a sensible thing to do in 3.6, 3.5 and 2.7 regardless of what happens in 3.7. For 3.7, I don't understand the trade-offs well enough to have a strong opinion, but dropping the feature entirely does seem reasonable - folks that want fine-grained floating point exception control these days are likely to be much better served by the decimal module, or one of the third party computing libraries (numpy, gmpy, sympy, etc). There was a thread back in 2012 [1] regarding the possibility of instead updating floats to offer flexibility similar to that offered by those other modules, but I think our discussions of the expected semantics of a decimal literal show that that would be a bad idea - context dependent behaviour in numeric literals creates all sorts of problems at the level of compiler and interpreter design. Cheers, Nick. [1] https://mail.python.org/pipermail/python-ideas/2012-October/016768.html -- Nick Coghlan | [email protected] | Brisbane, Australia ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
