Re: [python-committers] A different way to focus discussions

2018-07-11 Thread Guido van Rossum
On Wed, Jul 11, 2018 at 11:22 AM, Mariatta Wijaya  wrote:

>
> For permalink in zulip, the link from "Copy link to conversation" seems to
> be sufficient.
> I've created a stream (https://python.zulipchat.com/
> #narrow/stream/130206-.23pep581/subject/hello/near/129486993) but it now
> has double ##  and it seems I can't rename it to remove the extra "#"
>
> I've been waiting for the "excitement" surrounding PEP 572 to cool down
> before I want to merge PEP 581 (https://github.com/python/peps/pull/681/)
>

I'm posting the acceptance later today.


> I was hoping to bypass python-ideas since we've discussed at Python
> Language Summit :)  but if really needed I can start a thread there.
>

>From my reading of the summit, most people were okay with exploring this,
but many had specific issues they thought needed to be researched and
addressed in the PEP. And many core devs (the majority, actually, depending
on how you count :-) were not at the summit. I guess since it's mostly the
core devs that need to be convinced, announcing the Zulip channel here is
good enough, unless we hear from people for whom Zulip doesn't work at all.
So if you don't want to go to python-ideas, you have my blessing.


> Mariatta
>
>
> On Wed, Jul 11, 2018 at 10:38 AM Guido van Rossum 
> wrote:
>
>> I like the Zulip idea, though it'll be hard to get permalinks to past
>> discussions.
>>
>> Also, before going to python-dev it should probably be battle-tested in
>> python-ideas (PEP 572 wasn't ready for python-dev when it was moved there,
>> and I'm still recovering from the resulting brawl).
>>
>> On Wed, Jul 11, 2018 at 10:31 AM, Ethan Furman 
>> wrote:
>>
>>> On 07/11/2018 09:25 AM, Mariatta Wijaya wrote:
>>>
>>> Sorry to bring up this old topic.

 I'm trying to decide how to handle discussions for PEP 581, and I'm
 open to try out new things :)
 Are we all still content with posting to python-dev?
 I was thinking in addition to a thread in python-dev, I want to allow
 discussions to take place in zulip, under a new
 #pep581 stream.
 Will that be ok?

>>>
>>> I think this will be a good test of Zulip, as well as incentive for
>>> folks to join.
>>>
>>> --
>>> ~Ethan~
>>>
>>>
>>> ___
>>> python-committers mailing list
>>> python-committers@python.org
>>> https://mail.python.org/mailman/listinfo/python-committers
>>> Code of Conduct: https://www.python.org/psf/codeofconduct/
>>>
>>
>>
>>
>> --
>> --Guido van Rossum (python.org/~guido)
>> ___
>> python-committers mailing list
>> python-committers@python.org
>> https://mail.python.org/mailman/listinfo/python-committers
>> Code of Conduct: https://www.python.org/psf/codeofconduct/
>>
>


-- 
--Guido van Rossum (python.org/~guido)
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/


Re: [python-committers] A different way to focus discussions

2018-07-11 Thread Brett Cannon
I just renamed the stream so there's now just a single #. :)

On Wed, 11 Jul 2018 at 11:22 Mariatta Wijaya 
wrote:

>
> For permalink in zulip, the link from "Copy link to conversation" seems to
> be sufficient.
> I've created a stream (
> https://python.zulipchat.com/#narrow/stream/130206-.23pep581/subject/hello/near/129486993)
> but it now has double ##  and it seems I can't rename it to remove the
> extra "#"
>
> I've been waiting for the "excitement" surrounding PEP 572 to cool down
> before I want to merge PEP 581 (https://github.com/python/peps/pull/681/)
>
> I was hoping to bypass python-ideas since we've discussed at Python
> Language Summit :)  but if really needed I can start a thread there.
>
> Mariatta
>
>
> On Wed, Jul 11, 2018 at 10:38 AM Guido van Rossum 
> wrote:
>
>> I like the Zulip idea, though it'll be hard to get permalinks to past
>> discussions.
>>
>> Also, before going to python-dev it should probably be battle-tested in
>> python-ideas (PEP 572 wasn't ready for python-dev when it was moved there,
>> and I'm still recovering from the resulting brawl).
>>
>> On Wed, Jul 11, 2018 at 10:31 AM, Ethan Furman 
>> wrote:
>>
>>> On 07/11/2018 09:25 AM, Mariatta Wijaya wrote:
>>>
>>> Sorry to bring up this old topic.

 I'm trying to decide how to handle discussions for PEP 581, and I'm
 open to try out new things :)
 Are we all still content with posting to python-dev?
 I was thinking in addition to a thread in python-dev, I want to allow
 discussions to take place in zulip, under a new
 #pep581 stream.
 Will that be ok?

>>>
>>> I think this will be a good test of Zulip, as well as incentive for
>>> folks to join.
>>>
>>> --
>>> ~Ethan~
>>>
>>>
>>> ___
>>> python-committers mailing list
>>> python-committers@python.org
>>> https://mail.python.org/mailman/listinfo/python-committers
>>> Code of Conduct: https://www.python.org/psf/codeofconduct/
>>>
>>
>>
>>
>> --
>> --Guido van Rossum (python.org/~guido)
>> ___
>> python-committers mailing list
>> python-committers@python.org
>> https://mail.python.org/mailman/listinfo/python-committers
>> Code of Conduct: https://www.python.org/psf/codeofconduct/
>>
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/


Re: [python-committers] A different way to focus discussions

2018-07-11 Thread Mariatta Wijaya
For permalink in zulip, the link from "Copy link to conversation" seems to
be sufficient.
I've created a stream (
https://python.zulipchat.com/#narrow/stream/130206-.23pep581/subject/hello/near/129486993)
but it now has double ##  and it seems I can't rename it to remove the
extra "#"

I've been waiting for the "excitement" surrounding PEP 572 to cool down
before I want to merge PEP 581 (https://github.com/python/peps/pull/681/)

I was hoping to bypass python-ideas since we've discussed at Python
Language Summit :)  but if really needed I can start a thread there.

Mariatta


On Wed, Jul 11, 2018 at 10:38 AM Guido van Rossum  wrote:

> I like the Zulip idea, though it'll be hard to get permalinks to past
> discussions.
>
> Also, before going to python-dev it should probably be battle-tested in
> python-ideas (PEP 572 wasn't ready for python-dev when it was moved there,
> and I'm still recovering from the resulting brawl).
>
> On Wed, Jul 11, 2018 at 10:31 AM, Ethan Furman  wrote:
>
>> On 07/11/2018 09:25 AM, Mariatta Wijaya wrote:
>>
>> Sorry to bring up this old topic.
>>>
>>> I'm trying to decide how to handle discussions for PEP 581, and I'm open
>>> to try out new things :)
>>> Are we all still content with posting to python-dev?
>>> I was thinking in addition to a thread in python-dev, I want to allow
>>> discussions to take place in zulip, under a new
>>> #pep581 stream.
>>> Will that be ok?
>>>
>>
>> I think this will be a good test of Zulip, as well as incentive for folks
>> to join.
>>
>> --
>> ~Ethan~
>>
>>
>> ___
>> python-committers mailing list
>> python-committers@python.org
>> https://mail.python.org/mailman/listinfo/python-committers
>> Code of Conduct: https://www.python.org/psf/codeofconduct/
>>
>
>
>
> --
> --Guido van Rossum (python.org/~guido)
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/


Re: [python-committers] A different way to focus discussions

2018-07-11 Thread Guido van Rossum
I like the Zulip idea, though it'll be hard to get permalinks to past
discussions.

Also, before going to python-dev it should probably be battle-tested in
python-ideas (PEP 572 wasn't ready for python-dev when it was moved there,
and I'm still recovering from the resulting brawl).

On Wed, Jul 11, 2018 at 10:31 AM, Ethan Furman  wrote:

> On 07/11/2018 09:25 AM, Mariatta Wijaya wrote:
>
> Sorry to bring up this old topic.
>>
>> I'm trying to decide how to handle discussions for PEP 581, and I'm open
>> to try out new things :)
>> Are we all still content with posting to python-dev?
>> I was thinking in addition to a thread in python-dev, I want to allow
>> discussions to take place in zulip, under a new
>> #pep581 stream.
>> Will that be ok?
>>
>
> I think this will be a good test of Zulip, as well as incentive for folks
> to join.
>
> --
> ~Ethan~
>
>
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>



-- 
--Guido van Rossum (python.org/~guido)
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/


Re: [python-committers] A different way to focus discussions

2018-07-11 Thread Brett Cannon
On Wed, 11 Jul 2018 at 10:31 Ethan Furman  wrote:

> On 07/11/2018 09:25 AM, Mariatta Wijaya wrote:
>
> > Sorry to bring up this old topic.
> >
> > I'm trying to decide how to handle discussions for PEP 581, and I'm open
> to try out new things :)
> > Are we all still content with posting to python-dev?
> > I was thinking in addition to a thread in python-dev, I want to allow
> discussions to take place in zulip, under a new
> > #pep581 stream.
> > Will that be ok?
>
> I think this will be a good test of Zulip, as well as incentive for folks
> to join.
>

Fine by me as well since we won't know if it will work until we try it. :)
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/


Re: [python-committers] A different way to focus discussions

2018-07-11 Thread Ethan Furman

On 07/11/2018 09:25 AM, Mariatta Wijaya wrote:


Sorry to bring up this old topic.

I'm trying to decide how to handle discussions for PEP 581, and I'm open to try 
out new things :)
Are we all still content with posting to python-dev?
I was thinking in addition to a thread in python-dev, I want to allow 
discussions to take place in zulip, under a new
#pep581 stream.
Will that be ok?


I think this will be a good test of Zulip, as well as incentive for folks to 
join.

--
~Ethan~

___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/


Re: [python-committers] A different way to focus discussions

2018-07-11 Thread Mariatta Wijaya
Sorry to bring up this old topic.

I'm trying to decide how to handle discussions for PEP 581, and I'm open to
try out new things :)
Are we all still content with posting to python-dev?
I was thinking in addition to a thread in python-dev, I want to allow
discussions to take place in zulip, under a new #pep581 stream.
Will that be ok?


Mariatta


On Thu, Jun 28, 2018 at 4:34 AM Antoine Pitrou  wrote:

>
> Le 28/06/2018 à 13:04, Victor Stinner a écrit :
> > It seems like the PEP 572 discussions restarted on python-dev mailing
> > list with more than 100 emails in one week.
> >
> > Stupid idea: we created a mailing list just to fix os.random(): PEP
> > 522 and PEP 524, whereas these discussions were not the ones with the
> > most emails. Why not creating a new pep572 mailing list for the ones
> > who don't want to follow PEP 572 discussions?
>
> PEP 572 is a language-wide change.  Presumably those who don't want to
> follow discussions will still want to give their opinion (or informal
> vote) at the end.  Which will give rise to other discussions...
>
> What strikes me is that we have such long-lasting and intense discussion
> about a feature which, whether approved or not, will not significantly
> change Python's popularity or appeal or ability to solve real-world
> problems.
>
> Perhaps this is a case where « Nature abhors a vacuum » : we're getting
> focussed on whatever comes up to fill the narrative of Python's evolution.
>
> Regards
>
> Antoine.
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/