r culture be "discuss on BPO", but it will produce a much
>> superior history to what github PRs produce, so I think it is worth it.
>>
>
> I agree with David and MAL. github PR's should replace Rietveld for code
> reviews, and should not replace BPO for discussions
3. As an elected body, the accountaibility mechanism for Board level
> >> decision making is built into the PSF By-laws
> >> 4. The Board membership list at any given point in time is public
> >> information
> >> 5. The Board is already set up to handle confidential discussion of
> >> sensitive matters
> &g
ters?
> What if it was a core developer who was being rude, where can a non
> core-dev contributor report such behavior?
>
>
>
> Mariatta Wijaya
>
> On Thu, May 4, 2017 at 6:53 AM, Nick Coghlan wrote:
>
>> On 4 May 2017 at 06:10, Guido van Rossum wrote:
>> >
I saw this thread)
>
> Cheers,
> Nick.
>
> --
> Nick Coghlan | [email protected] | Brisbane, Australia
> ___
> python-committers mailing list
> [email protected]
> https://mail.python.org/m
hose occasions where having a dictator is useful.
>
> *DON'T WAIT*: September is closer than you think! Please let me know as
> soon as possible so we can start setting up the event. I'm going to close
> the sign-up form on June 23rd.
>
> Organizational-ly yours,
> Ł
>
_
> python-committers mailing list
> [email protected]
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
--
--Guido van Rossum (python.org/~guido)
___
p
__
> python-committers mailing list
> [email protected]
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
>
--
--Guido van Rossum (python.org/~guido)
_
>
I think it's a good idea in many cases, but not required. E.g. you may be
OK with the diff but still ask the author to clean up some small nits, and
then they can merge their own diff. Or you may be OK with the diff but want
to wait for
other reviewer's OK.
>
> Yeah, it's not uncommon that I prefer to get a second review. Usually,
> I explicitly say it in a comment.
>
> > The good news is that it's no longer wrong, since the author is preserved
> >
devs since it
seems the consensus that usually the author (if a core dev) wants to merge
their own work on their own time.
--
--Guido van Rossum (python.org/~guido)
___
python-committers mailing list
[email protected]
https://mail.python.org/
; Regards
>>
>> Antoine.
>> ___________
>> python-committers mailing list
>> [email protected]
>> https://mail.python.org/mailman/listinfo/python-committers
>> Code of Conduct: https://www.python.org/psf/codeofcond
d in yet
others (557, 563).
He is responsible for at least 16 commits in master.
I have worked with him for a long time on typing.py and on mypy (where he
is a core dev) and I can vouch for him completely.
--
--Guido van Rossum (python.org/~guido)
___
py
quest an approval by other
> core developers if he wants to touch other parts of CPython. In my
> experience, developers are already doing that naturally, but I would
> prefer to clarify this point.
>
> Victor
>
> 2017-12-06 2:00 GMT+01:00 Guido van Rossum :
> > I'
to give Ivan commit privileges when I
> was merging his PEP 526 implementation, so I think it's long overdue.
>
> Yury
>
> On Tue, Dec 5, 2017 at 8:00 PM, Guido van Rossum wrote:
> > I'd like to propose Ivan Levkivskyi as a new core committer. He's
> > (
I think I figured it out -- I invited him to the python org on GitHub.
Anything else?
On Wed, Dec 6, 2017 at 8:37 AM, Guido van Rossum wrote:
> OK, let's make it so. It's been a long time since I initiated a new
> committer -- what has to happen next? I just flipped his commit
gged into GitHub and pushes/pulls don’t require it.
>
> ___
> python-committers mailing list
> [email protected]
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.or
___
> >> python-committers mailing list
> >> [email protected]
> >> https://mail.python.org/mailman/listinfo/python-committers
> >> Code of Conduct: https://www.python.org/psf/codeofconduct/
> >>
> >
https://mail.python.org/mailman/listinfo/python-committers
>> Code of Conduct: https://www.python.org/psf/codeofconduct/
>>
>>
> ___________
> python-committers mailing list
> [email protected]
> https://mail.python.org/mai
Cool trick! Works on Sierra too. I guess it's all part of Apple's drive to
merge iOS and OS X...
On Sat, Jan 27, 2018 at 2:12 PM, Barry Warsaw wrote:
> On Jan 27, 2018, at 17:04, Guido van Rossum wrote:
>
>
> Hardly a surprising choice! Congrats, Łukasz. (And never forg
PRs to
be created?
--
--Guido van Rossum (python.org/~guido)
___
python-committers mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/
Ah. Makes sense. UI design is hard... Thanks!
On Thu, Feb 15, 2018 at 4:35 PM, Zachary Ware
wrote:
> On Thu, Feb 15, 2018 at 6:21 PM, Guido van Rossum
> wrote:
> > Occasionally I receive a sequence of emails from GitHub where a PR is
> > requesting my review by some user, t
mmitters because I now fear that I would
> get too many replies on python-dev ...
>
> Victor
> ___
> python-committers mailing list
> [email protected]
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Cond
is cancelled. Oh oh.
>
> Victor
> ___
> python-committers mailing list
> [email protected]
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
.org/psf/codeofconduct/
>>
>> ___
> python-committers mailing list
> [email protected]
> 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
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/
plies.
>
> Wait. Mark is already a core dev, right? I don't understand your email :-)
>
> +1, obvisouly.
>
> Victor
> ___
> python-committers mailing list
> [email protected]
> https://mail.python.org/mailman/listi
it please let me know.
>>
>> Thanks.
>> Eric
>> ___
>> python-committers mailing list
>> [email protected] <mailto:[email protected]>
>> https://mail.python.org/mail
//youtu.be/hhj7eb6TrtI
>
> On Tue, May 15, 2018, 11:35 AM Guido van Rossum wrote:
>
>> Let's stop the email barrage, Mark is in. Can someone tell Mark what to
>> do?
>>
>>
--
--Guido van Rossum (python.org/~guido)
__
to subscribe to all peps traffic.
Thoughts? (We can dogfood this proposal too, if there's interest. :-)
--
--Guido van Rossum (python.org/~guido)
___
python-committers mailing list
[email protected]
https://mail.python.org/mailman/listin
others, and attempts to move all PEPs to a subdirectory have also failed,
due to perpetual lack of resources to complete the task (and e.g. the need
to update scripts on python.org whenever the peps repo structure changes).
>
> --
> Ivan
>
>
>
> On 18 May 2018 at 18:25, Guid
Yes, you can do that.
On Fri, May 18, 2018, 16:51 Ivan Levkivskyi wrote:
> On 18 May 2018 at 19:46, Gregory P. Smith wrote:
>
>>
>> I'm all for picking a victom^Wvolunteer PEP to try dogfood it on.
>>
>>
> Can few related PEPs share the same repository? For example, I want to
> start writing th
On Tue, May 22, 2018 at 11:58 AM, Barry Warsaw wrote:
> [I think my other response got dropped, so apologies for any duplicates]
>
> Guido van Rossum wrote:
> > I wonder if it would make sense to require that for each PEP a new GitHub
> > *repo* be created whose contents
On Tue, May 22, 2018 at 2:50 PM, Victor Stinner wrote:
> 2018-05-19 0:25 GMT+02:00 Guido van Rossum :
> > Discussing PEPs on python-dev and python-ideas is clearly not scalable
> any
> > more. (Even python-committers probably doesn't scale too well. :-)
> >
> >
st
> [email protected]
> 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
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/
t
> [email protected]
> 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
pytho
e clean up for dev access on the
> repository.
> ___
> python-committers mailing list
> [email protected]
> 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
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/
t; us and posted it to all friends, YES! :-)
>
> That said: I would fully understand if my status was changed to “dormant
> core dev” or “retired core dev” and I wouldn’t have any problems with that.
>
> Jack
>
>
> On 18-Jun-2018, at 21:07 , Guido van Rossum wrote:
>
> Hm, un
at mean the logo disappears? There
> is value in having the logo show up when commenting.
>
> —Chris
>
> On Mon, Jun 18, 2018 at 1:52 PM Paul Moore wrote:
>
>> On 18 June 2018 at 20:41, M.-A. Lemburg wrote:
>> > On 18.06.2018 21:07, Guido van Rossum wrote:
>&g
On Mon, Jun 18, 2018 at 10:12 PM Tal Einat wrote:
> On Tue, Jun 19, 2018 at 3:54 AM, Guido van Rossum
> wrote:
> >
> > If we currently have a list of core devs we should by default change
> people's status to emeritus core dev when they choose (c). They may also
> c
2018 at 11:23 AM Brett Cannon wrote:
>
>
> On Mon, 18 Jun 2018 at 17:56 Guido van Rossum wrote:
>
>> I'd do it as follows. This basically makes withdrawal voluntary unless
>> they don't respond at all.
>>
>> 1. Make a list of people who've no
wrote:
> > On Mon, 18 Jun 2018 at 17:56 Guido van Rossum wrote:
>
> >> I'd do it as follows. This basically makes withdrawal voluntary unless
> >> they don't respond at all.
> >>
> >> 1. Make a list of people who've not shown any sign of a
1 vote
>
>
>
> * Serhiy Storchaka ("-0")
>
>
>
> Victor
>
> ___
>
> python-committers mailing list
>
> [email protected]
>
> https://mail.python.org/mailman/listinfo/python-committers
>
>
> ___
> python-committers mailing list
> [email protected]
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
--
--Guido van Rossum (python.org/~guido
eek or the week
after. There are also several minor TODOs in the PEP that need to be
resolved.
I will sort it all out, just please be patient.
--
--Guido van Rossum (python.org/~guido)
___
python-committers mailing list
python-committers@python
k this will be a good test of Zulip, as well as incentive for folks
> to join.
>
> --
> ~Ethan~
>
>
> ___
> python-committers mailing list
> [email protected]
> https://mail.python.org/mailman/listinfo/p
r 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 permalink
hough membership
is closed (limited to core devs).
I'll still be here, but I'm trying to let you all figure something out for
yourselves. I'm tired, and need a very long break.
--
--Guido van Rossum (python.org/~guido)
___
python-committe
I’m still here, but I would like to be out of the debate and out of the
decision loop. I’m also still President of the PSF. But this is not for the
PSF to decide. You all are doing fine.
—Guido
On Sun, Jul 15, 2018 at 1:37 PM Brett Cannon wrote:
>
>
> On Sun, Jul 15, 2018, 13:01 Thomas Wouters,
W00t! 🎂🍰🥧🍦🍮🍨🍧🍱
On Tue, Sep 11, 2018 at 1:48 PM Mariatta Wijaya
wrote:
> I've deployed the bot to automerge CPython pull request on the master
> branch.
>
> One benefit of this is you don't need to worry about replacing "#" into
> "GH-".
>
> To get the bot to automerge:
> - first edit the PR titl
> talks: https://www.youtube.com/watch?v=hKxbO4rRlpg and
> https://www.youtube.com/watch?v=ww1UsGZV8fQ
> ___
> python-committers mailing list
> [email protected]
> https://mail.python.org/mailman/listinfo/pyth
-
--Guido van Rossum (python.org/~guido)
___
python-committers mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/
ns and attendee registrations tend to happen immediately before
the deadline.
I propose not to move the deadline *unless* the PEP authors ask for an
extension on the eve of Oct 1st.
--
--Guido van Rossum (python.org/~guido)
___
python-committers mailing list
t it's well documented that diverse group make
better decisions. And given that there is a historical bias, often
unconscious, towards white men I think it's good to try to counter this
bias explicitly.
I should also think that "merit-based" criteria tend to reinforce the
exi
info about them. But staying informed as a voter
is work, and if you care about this community, you'll have to do that work.
Getting to know a new online tool isn't going to kill you.
--
--Guido van Rossum (python.org/~guido)
___
python-commi
ore dev, so he doesn’t
> have
> > a horse in this race). Although I don’t really care who runs it, I think
> anyone
> > here is going to be honest about it.
> >
> > I can say as a supervisor you also can’t see how people have voted at
> all until
> > after the voting ends. You can only see how many peop
;> ___
> >> python-committers mailing list
> >> [email protected]
> >> https://mail.python.org/mailman/listinfo/python-committers
> >> Code of Conduct: https://www.python.org/psf/codeofconduct/
e vote-getters are:
>
> - Barry Warsaw
> - Brett Cannon
> - Carol Willing
> - Guido van Rossum
> - Nick Coghlan
>
> No conflict of interest as defined in PEP 13 were observed.
>
> Eligible voters have received result notification emails from helios, and
> may return to
>
I would wait until you have explicit permission from every candidate. (You
probably will have to reach out to some.) I hereby grant you mine.
--
--Guido van Rossum (python.org/~guido)
___
python-committers mailing list
[email protected]
issues and
> PRs. ;)
>
>
> But you realize that this a feature, not a bug? :)
>
> https://blog.codinghorror.com/web-discussions-flat-by-design/
>
Thanks for the link. I'm convinced. (No sarcasm.)
--
--Guido van Rossum (python.org/~guido)
_
Note that it would have to be in the Committers topic.
On Fri, Mar 22, 2019 at 11:45 AM Brett Cannon wrote:
> We discussed this and we think an anonymous vote on discuss.python.org is
> probably best for this sort of thing.
>
> Victor, did you want to do the poll or would you prefer I set it up?
hat this PEP will be postponed until Python 3.9.)
- PEP 586, PEP 589, PEP 591 (various typing PEPs by members of the
mypy team and others, topics Literal, TypedDict, and Final).
*Appointed Guido van Rossum as BD.* (PEP 544, Protocols, also
belongs in this list; Guido made himself BD las
is always going to remain controversial. I have one request: please
don't start a vote or poll.
--
--Guido van Rossum (python.org/~guido)
*Pronouns: he/him/his **(why is my pronoun here?)*
<http://feministing.com/2015/02/03/how-using-they-as-a-singular-pronoun-can
On Sun, Apr 28, 2019 at 2:05 PM Ezio Melotti wrote:
> On Sat, Apr 27, 2019 at 10:44 PM Guido van Rossum
> wrote:
> >
> > On Sat, Apr 27, 2019 at 11:10 AM Victor Stinner
> wrote:
> >>
> >> Would it be possible to discuss these PEPs on python-dev? Or is
Thanks!
On Wed, May 1, 2019 at 15:26 Brett Cannon wrote:
> The vote has closed and the ayes have it with 85% of the vote. Thanks to
> everyone who participated!
>
> On Wed, Apr 17, 2019 at 1:01 PM Brett Cannon wrote:
>
>>
>> https://discuss.python.org/t/vote-on-pep-13-change-to-specify-voting-t
[email protected]/message/Q64NROQCBD43RLF5B77CZQFYCSAASBG7/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
--
--Guido van Rossum (python.org/~guido)
*Pronouns: he/him/his **(why is my pronoun here?)*
<http://feministing.com/2015/02/03/how-using-they-as-a-singul
O7YR4V6JDWX3FA2OA5/
> > Code of Conduct: https://www.python.org/psf/codeofconduct/
> ___
> python-committers mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> https://mail.pyt
Once a core dev, always a core dev (unless you’re fired). Git permissions
can be reinstated no questions asked.
On Wed, Dec 4, 2019 at 15:25 Victor Stinner wrote:
> If a core dev asks to have their commit bit removed, what happens if
> they change their mind? Do we have go through the usual vote
Yes, congrats Batuhan!
On Fri, Feb 7, 2020 at 07:28 Carol Willing wrote:
> Congrats Batuhan! Thanks for contributing to CPython :D
>
> On Fri, Jan 31, 2020 at 12:59 PM Pablo Galindo Salgado <
> [email protected]> wrote:
>
>> Hi,
>>
>> I have been mentoring Batuhan Taskaya ("BTaskaya" on BPO, "
The solution seems obvious: move to GitHub. :-)
On Fri, Feb 28, 2020 at 11:51 Antoine Pitrou wrote:
>
> Le 28/02/2020 à 19:56, Mariatta a écrit :
> > I think this is same issue
> > as https://github.com/python/bugs.python.org/issues/38
> >
> > To get in touch with infrastructure team, you can wr
on.org/mailman3/lists/python-committers.python.org/
> Message archived at
> https://mail.python.org/archives/list/[email protected]/message/YE6LHAPPGVYD2NO77WAQOBF443LFC5XJ/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
--
--Guido van Rossum (python.org/~guido)
_
> python-committers mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived
inevitable that making
them the default will come up again, so the effort of writing up how it
could be done and what problems it would encounter won't be a waste.
--
--Guido van Rossum (python.org/~guido)
*Pronouns: he/him **(why is my pronoun here?)*
<http://feministing.com/2015/02/03/
Huge congrats, Pablo. And thanks to Lukasz for 3.8 and 3.9. They’re all the
greatest release ever!
On Tue, May 19, 2020 at 15:54 Barry Warsaw wrote:
> In light of the release of Python 3.9b1, let’s take a moment to celebrate
> all the great work that our Python 3.8 and 3.9 release manager Łukasz
Once the release happens, bug fixes and
> documentation tweaks will continue to be checked in for the next
> micro-release.
>
I've occasionally left it up to Łukasz to add the "needs 3.9 backport"
label to a PR of mine. That seems a good way to keep the release manager
happy. :-
Hi y'all,
Pablo and I have opened a poll to promote Brandt Bucher as a core developer.
https://discuss.python.org/t/vote-to-promote-brandt-bucher/5135
Please vote!
Be safe, be well,
--Guido and Pablo
--
--Guido van Rossum (python.org/~guido)
*Pronouns: he/him **(why is my pronoun
/mail.python.org/archives/list/[email protected]/message/QGIHFU64TBYT56K6M5A5LYTYTSVFKHWQ/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
--
--Guido van Rossum (python.org/~guido)
*Pronouns: he/him **(why is my pronoun here?)*
<http://feministing.com/2015/02/03/how
Once issues move to GitHub we’ll have this with no additional effort.
On Sun, Oct 11, 2020 at 12:14 Gregory P. Smith wrote:
> We've got the automerge tag on GH, it+bot make it awesome. There's one
> more thing I'd like to see that could help with bug hygiene: A tag to close
> the associated bug
LVLO5CHW2WT6ZZNRNSKDID/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
--
--Guido van Rossum (python.org/~guido)
*Pronouns: he/him **(why is my pronoun here?)*
<http://feministing.com/2015/02/03/how-using-they-as-a-singular-pronoun-can-change-the-world/>
___
.org
> To unsubscribe send an email to [email protected]
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at
> https://mail.python.org/archives/list/[email protected]/message/O3CC7U2ERJLUCJRE7UOE7GIXME
I got this too on two forks of cpython. It smells like a dependabot mistake.
On Tue, Dec 1, 2020 at 04:59 Terry Reedy wrote:
> This morning I woke to find that dependabot had added two new branches
> to my cpython fork
> https://github.com/terryjreedy/cpython/branches
> and had created correspon
pendabot. This open ticket seems related
> https://github.com/dependabot/dependabot-core/issues/2804
>
> On Tue., Dec. 1, 2020, 7:36 a.m. Guido van Rossum,
> wrote:
>
>> I got this too on two forks of cpython. It smells like a dependabot
>> mistake.
>>
>>
//mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at
> https://mail.python.org/archives/list/[email protected]/message/BGNVTKM4YRHTOVRJEWZQ6DFZFGVORHF3/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
--
--Guido van Rossum (python.o
cribe send an email to [email protected]
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at
> https://mail.python.org/archives/list/[email protected]/message/A6B52BFBLLOSKEX2GXUKNBFPXREO5PKB/
> Code of Conduct: https://ww
interface -- Tk has a method named `raise`, but
> it has to be renamed to tkraise because of the
> keyword clash (it's also given a `lift` alias).
>
This is a reasonable idea, with definite pros and cons. I recommend
starting a separate thread about that.
--
--Guido van Ros
t; One day, we will silently switch Python to UTF-8 by default, and
> nobody will notice! ;-)
>
In particular it's important that nobody living in Japan or China should
notice. This is also still the biggest challenge. :-(
--
--Guido van Rossum (python.org/~guido)
*Pronouns: he/him **(
l clone of
cpython to it. I'll ask Zooba what he did.
--
--Guido van Rossum (python.org/~guido)
*Pronouns: he/him **(why is my pronoun here?)*
<http://feministing.com/2015/02/03/how-using-they-as-a-singular-pronoun-can-change-the-world/>
___
pyth
Mariatta, maybe this info helps the GitHub folks figure out how to fix this.
On Tue, Apr 6, 2021 at 10:02 AM Guido van Rossum wrote:
> I don't have much to add (this occurs to me too and I just bulk-delete the
> messages) but I wonder if the problem might be caused by a situation w
on.org/mailman3/lists/python-committers.python.org/
> Message archived at
> https://mail.python.org/archives/list/[email protected]/message/CLVXXPQ2T2LQ5MP2Y53VVQFCXYWQJHKZ/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
--
--Guido van Rossum (python.org/~
Recently it seems that when a PR linked to a bpo issue is merged, no note
of this event is made in the bpo issue. Look at
https://bugs.python.org/issue43933 for example. There are notes for the
first two merged PRs (25717 and 25719), at
https://bugs.python.org/issue43933#msg392343 and the next mess
I’ve found Gitter works well. I’d use that, assuming it was only open to
core devs and invitees.
On Thu, May 13, 2021 at 16:39 Senthil Kumaran wrote:
> Hello Core Dev,
>
> I find a need for a core-dev chat service, wherein I could engage in
> some quick effervescent conversations.
>
> It is like
I'm guessing we have to escalate this to Ee.
On Mon, May 17, 2021 at 2:58 PM Victor Stinner wrote:
> Any update on this issue? Nobody recalls what code and service sends a
> comment to bugs.python.org when a commit is merged?
>
> Victor
>
> On Wed, May 12, 2021 at 4
ical discussions are
archived for posterity. We should be careful not to have discussions that
lead to decisions on such a chat channel, because that excludes others who
either weren't there at the time (all chats are terrible when there's a lot
of scrollback, almost by design) or wh
On Sat, May 22, 2021 at 2:41 PM Senthil Kumaran wrote:
> On Sat, May 22, 2021 at 01:54:23PM -0700, Guido van Rossum wrote:
>
> > 2. I can handle Discord just fine nowadays but *please* don't combine
> this with
> > the Python Discord server.
>
> This was expr
Europe for example?)
On Sat, May 22, 2021 at 21:41 Kyle Stanley wrote:
> On Sat, May 22, 2021 at 4:54 PM Guido van Rossum wrote:
>
>> 2. I can handle Discord just fine nowadays but *please* don't combine
>> this with the Python Discord server. That server is super acti
s.python.org/
> Message archived at
> https://mail.python.org/archives/list/[email protected]/message/FVJGITXYCWDNUQYS553LQVEQPFUQTM6R/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
--
--Guido van Rossum (python.org/~guido)
*Pronouns: he/him **(why is my pronou
rom bpo for about a week now. Maybe it
> had enough of me.
>
> On Thu, May 27, 2021 at 6:01 PM Victor Stinner
> wrote:
>
>> I confirm that commits merged in 3.9, 3.10 and main branches are
>> logged again in bugs.python.org. Thanks to everyone who helped to
>> solve
Travis-CI it did exist, but only for privileged users. Does GitHub Actions
have such a thing?
Example: https://github.com/python/cpython/pull/25551 -- the Address
Sanitizer run has been waiting for 19 hours.
--
--Guido van Rossum (python.org/~guido)
*Pronouns: he/him **(why is my pronoun here
(I've asked for this when they've done research sessions).
>
> FWIW, I'd recommend adding a timeout to jobs (it can be set in the YML
> file), that way hung jobs don't hang for hours and hours.
>
> Alex
>
> On Tue, Jun 22, 2021 at 3:16 PM Guido van Rossum wr
have to wait 19 hours to do so (github
> actions also doesn't let you restart jobs until they're all completed,
> or cancelled I suppose).
>
> Alex
>
> On Tue, Jun 22, 2021 at 3:54 PM Guido van Rossum wrote:
> >
> > That's too bad, we really should ask f
I would hope we’d remove it. It’s a toy implementation, unmaintained,
probably doesn’t support a lot of newer protocol features, and is probably
full of bugs. Hopefully nobody uses it!
On Tue, Jun 22, 2021 at 17:51 Irit Katriel via python-committers <
[email protected]> wrote:
> The do
There’s another possible explanation. This mailing list is archived and the
archives are publicly readable.
On Tue, Jun 29, 2021 at 22:07 Tim Peters wrote:
> Just for interest, I noticed a failed login attempt to my Github
> account about two hours ago, originating in Toronto.
>
> That's the fir
1 - 100 of 205 matches
Mail list logo
