Re: [Python-Dev] Reminder: 12 weeks to 3.7 feature code cutoff

On 4 November 2017 at 09:52, Jelle Zijlstra wrote: > > 2017-11-03 16:44 GMT-07:00 Joao S. O. Bueno : >> >> This just popped up in Brython's issue tracker discussion: >> >> """ >> Pierre Quentel >> >> 04:57 (16 hours ago)

Re: [Python-Dev] Reminder: 12 weeks to 3.7 feature code cutoff

2017-11-04 0:44 GMT+01:00 Joao S. O. Bueno : > This just popped up in Brython's issue tracker discussion: > > """ > Pierre Quentel > > 04:57 (16 hours ago) > to brython-dev/br., Subscribed > > I think it's better to rename all occurences of async

Re: [Python-Dev] Reminder: 12 weeks to 3.7 feature code cutoff

2017-11-03 16:44 GMT-07:00 Joao S. O. Bueno : > This just popped up in Brython's issue tracker discussion: > > """ > Pierre Quentel > > 04:57 (16 hours ago) > to brython-dev/br., Subscribed > > I think it's better to rename all occurences of async

Re: [Python-Dev] Reminder: 12 weeks to 3.7 feature code cutoff

This just popped up in Brython's issue tracker discussion: """ Pierre Quentel 04:57 (16 hours ago) to brython-dev/br., Subscribed I think it's better to rename all occurences of async now, although it's strange that : there is currently no deprecation warning in

Re: [Python-Dev] Reminder: 12 weeks to 3.7 feature code cutoff

Maybe we should remove typing from the stdlib? https://github.com/python/typing/issues/495 -- --Guido van Rossum (python.org/~guido) ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe:

Re: [Python-Dev] Reminder: 12 weeks to 3.7 feature code cutoff

Terry Reedy writes: > On 11/2/2017 4:54 AM, Lele Gaifax wrote: > >> I'm not sure if the rebase should have been done on the original branch >> instead of creating a new one, or instead if I should open a new PR (and >> close the original one?). > > It is normal to 'git merge

Re: [Python-Dev] Reminder: 12 weeks to 3.7 feature code cutoff

I will be happy to see PEP 544 and PEP 560 in Python 3.7, and maybe also PEP 562 (if we decide on it and I will have time). -- Ivan ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe:

Re: [Python-Dev] Reminder: 12 weeks to 3.7 feature code cutoff

On 11/1/2017 5:47 PM, Ned Deily wrote: Happy belated Halloween to those who celebrate it; I hope it wasn't too scary! Also possibly scary: we have just a little over 12 weeks remaining until Python 3.7's feature code cutoff, 2018-01-29. Those 12 weeks include a number of traditional

Re: [Python-Dev] Reminder: 12 weeks to 3.7 feature code cutoff

On 11/2/2017 4:54 AM, Lele Gaifax wrote: I'm not sure if the rebase should have been done on the original branch instead of creating a new one, or instead if I should open a new PR (and close the original one?). It is normal to 'git merge upstream/master' after updating the master branch and

Re: [Python-Dev] Reminder: 12 weeks to 3.7 feature code cutoff

> On 1 Nov 2017, at 22:47, Ned Deily wrote: > > Happy belated Halloween to those who celebrate it; I hope it wasn't too > scary! Also possibly scary: we have just a little over 12 weeks remaining > until Python 3.7's feature code cutoff, 2018-01-29. Those 12 weeks include a

Re: [Python-Dev] Reminder: 12 weeks to 3.7 feature code cutoff

Hi, I'd like to know what should I do wrt to issue #27645 [1] and the related PR #377 [2]: I think I fulfilled every requested item, and a month ago I rebased the work [3] to solve the NEWS conflicts. I'm not sure if the rebase should have been done on the original branch instead of creating a