Re: [Python-Dev] New poll about a macro for safe reference replacing

2015-12-23 Thread Stephen J. Turnbull
Serhiy Storchaka writes: > This would be a voluntarism. You did due diligence, took the poll, and got additional information as well. It is *very* clear to me at least that you are paying full attention to the poll. Yes, the bikeshedding should end but I think you should do as you think best i

Re: [Python-Dev] Typo in PEP-0423

2015-12-23 Thread Chris Jerdonek
On Tue, Dec 22, 2015 at 4:35 PM, Benjamin Peterson wrote: > We've played around with robots.txt, but it's still useful for old docs > to be indexed (e.g., for removed features), which just need to figure > out how to get them deprecation in results. I wonder if ref="canonical"> in the old docs wo

Re: [Python-Dev] New poll about a macro for safe reference replacing

2015-12-23 Thread Meador Inge
On Wed, Dec 23, 2015 at 9:08 AM, Nick Coghlan wrote: > Within the Python context, the analogy from setattr and setitem at the > Python level to Py_SETREF at the C level is pretty solid, so it likely > makes sense to run with that as "good enough". > > In regards to Py_MOVEREF, while other langua

Re: [Python-Dev] New poll about a macro for safe reference replacing

2015-12-23 Thread Nick Coghlan
On 24 December 2015 at 00:50, Serhiy Storchaka wrote: > On 22.12.15 18:36, Meador Inge wrote: >> >> On Tue, Dec 22, 2015 at 3:58 AM, Serhiy Storchaka > > wrote: >> >> On 21.12.15 23:57, Steve Dower wrote: >> >> Was Py_MOVEREF (or MOVE_REF) ever suggested? >>

Re: [Python-Dev] New poll about a macro for safe reference replacing

2015-12-23 Thread Serhiy Storchaka
On 23.12.15 16:52, Chris Angelico wrote: On Thu, Dec 24, 2015 at 1:50 AM, Serhiy Storchaka wrote: Oh, I'm confused. Should I make a new poll? With new voters Py_MOVEREF can get more votes than Py_SETREF. I suggest cutting off the bikeshedding. Both of these options have reasonable support. Pi

Re: [Python-Dev] New poll about a macro for safe reference replacing

2015-12-23 Thread Chris Angelico
On Thu, Dec 24, 2015 at 1:50 AM, Serhiy Storchaka wrote: > Oh, I'm confused. Should I make a new poll? With new voters Py_MOVEREF can > get more votes than Py_SETREF. I suggest cutting off the bikeshedding. Both of these options have reasonable support. Pick either and run with it, and don't worr

Re: [Python-Dev] New poll about a macro for safe reference replacing

2015-12-23 Thread Serhiy Storchaka
On 22.12.15 18:36, Meador Inge wrote: On Tue, Dec 22, 2015 at 3:58 AM, Serhiy Storchaka mailto:storch...@gmail.com>> wrote: On 21.12.15 23:57, Steve Dower wrote: Was Py_MOVEREF (or MOVE_REF) ever suggested? This would be nice name. The macro moves the ownership. But I think