Greetings!
I was recently added as a core-dev (yes, saying it still makes me smile ;).
Python is an awesome language and I am happy to be a part of it.
Minor history: I authored PEP 409 (raise ... from None), and authored most of the reference implementation for Enums
(PEP 435). I've been
On 08/02/2013 01:25 PM, Larry Hastings wrote:
But speaking of adjusting the schedule, I'm also considering changing bumping
all the remaining release dates forward by
a day. Currently all the releases are on Saturdays, which means we always tag
on Friday. Ned Deily suggests instead we
tag on
Congratulations Welcome!
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
On 11/30/2013 04:16 PM, Brett Cannon wrote:
For python-ideas, if someone wants to allow Anatoly's posts through then I will
happily make them an admin of the list,
but I have to just admit I can't be trusted to do it objectively and I don't
want Anatoly to receive unjust treatment;
there's
On 01/06/2014 02:21 PM, Barry Warsaw wrote:
On Jan 06, 2014, at 01:34 PM, Larry Hastings wrote:
The thing is, I feel like this is borderline between bug fix and new feature.
But without adding this, we would make a lot of the Argument Clinic
conversions pretty messy. So I want to check it in.
On 01/16/2014 06:03 PM, � wrote:
And while I completely understand that core developers enjoy working in 3 much
more, it was decided to not accept any
improvements for a +2.7 version [...]
You mean, like, new features? Have any new features been put in 2.7 after it
hit feature freeze?
--
On 01/19/2014 02:06 PM, Victor Stinner wrote:
Is it enough to know the python process and how to write good patches?
I would say that's half the battle, but not all of it [1].
I don't see why Yury would become but not Vajrasky Kok.
I haven't worked with Yury, but I have worked with
On 02/01/2014 05:02 PM, Nick Coghlan wrote:
When PEP 450 (the statistics module) was accepted, it looks like we
missed the step of granting Steven commit access for module
maintenance purposes. We should probably fix that :)
+1
--
~Ethan~
___
On 04/15/2014 05:55 PM, R. David Murray wrote:
[...] I've changed the text associated with the 'invalid' resolution
to read 'not a bug' [...]
Nice.
Any chance of changing the 'committed/rejected' text to something else? :)
--
~Ethan~
___
On 04/18/2014 07:31 PM, R. David Murray wrote:
On Wed, 16 Apr 2014 10:53:53 -0400, R. David Murray rdmur...@bitdance.com
wrote:
On Tue, 15 Apr 2014 23:21:41 -0400, Terry Reedy tjre...@udel.edu wrote:
On 4/15/2014 9:45 PM, Ethan Furman wrote:
On 04/15/2014 05:55 PM, R. David Murray wrote
On 10/15/2014 01:25 PM, Eli Bendersky wrote:
On Mon, Oct 6, 2014 at 6:51 AM, Georg Brandl wrote:
On 10/06/2014 02:56 PM, Nick Coghlan wrote:
Why is Anatoly posting to python-dev? I thought he was banned when he was banned
from the tracker.
I refuse to waste my time trying to reason with him,
On 10/15/2014 01:54 PM, Antoine Pitrou wrote:
Le 15/10/2014 22:49, Ethan Furman a écrit :
I've been promoted to list-moderator for two other Python lists to help
deal with Anatoly's posts -- one more would not be a burden.
If the burden is mostly handling Anatoly's email, perhaps we should
For at least 24 hours now my attempts to connect to hg.python.org have been
futile.
I finally stuck to it this time, and about three minutes later finally got the
prompt, but after entering my password got a
remote: Connection closed by 104.130.43.97
abort: no suitable response from remote
On 03/10/2015 11:44 AM, Ethan Furman wrote:
For at least 24 hours now my attempts to connect to hg.python.org have been
futile.
I finally stuck to it this time, and about three minutes later finally got
the prompt, but after entering my password got a
remote: Connection closed
I like one massive patch, myself. :)
--
~Ethan~
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
On 07/14/2015 07:29 PM, Nick Coghlan wrote:
Would folks mind if I drafted a CPython Code of Conduct inspired by
their example, and proposed it for inclusion in the Developer's Guide?
Sounds good to me.
--
~Ethan~
___
python-committers mailing list
On 12/06/2015 07:25 PM, R. David Murray wrote:
> On Sun, 06 Dec 2015 17:09:25 -0800, Benjamin Peterson wrote:
>> On Sun, Dec 6, 2015, at 17:05, Jesus Cea wrote:
>>> I guess I had a DSA key in hg.python.org and those are not valid
>>> anymore, but looks like I am not a documented committer
On 12/15/2015 11:40 AM, Ethan Furman wrote:
> I cannot and will not be associated with a project that
> supports GitHub [...]
Lest anyone accuse me of hypocrisy because I have a GitHub account, it
is required for a class I am taking, and will be deleted (or at least go
unused) once that
On 12/12/2015 03:32 PM, Brett Cannon wrote:
> Over at core-workflow@ we are discussing details of the GitHub and
> GitLab proposals and one of the worries the GitLab supporters have
> brought up is that some core developers could flat-out stop
> contributing if we moved to GitHub. Now I have
On 12/15/2015 12:41 PM, Senthil Kumaran wrote:
> These are the follow-up articles which state that Github Inc has
> taken some actions to correct the "mistakes" they might have done.
>
> https://github.com/blog/1826-follow-up-to-the-investigation-results
>
On 12/15/2015 12:59 PM, Barry Warsaw wrote:
On Dec 15, 2015, at 12:41 PM, Senthil Kumaran wrote:
If we have doubts on the culture of the company, it may be a good idea to
talk directly to their public relations department or an informal chat with
women who currently work at Github and get a
On 01/01/2016 11:24 AM, Brett Cannon wrote:
Happy 2016 everyone, and here is to hoping we will have an easier
developer workflow by the end of this year!
Thanks for doing this, Brett!
I'm looking forward to an easier work flow.
--
~Ethan~
___
Question: I noticed a couple issues on b.p.o that were being closed by
contributors (not core-devs, not their own issues).
Should non-core-devs be closing issues that do not belong to them?
--
~Ethan~
___
python-committers mailing list
On 06/06/2016 10:17 AM, Brett Cannon wrote:
Some non-core devs have elevated privileges on the tracker to help with
issue triage.
So if they can, they've been granted the privilege? Cool.
--
~Ethan~
___
python-committers mailing list
On 02/28/2016 11:10 AM, Brett Cannon wrote:
I swear that I did not mean to pull a fast one or somehow exert some
influence to make this happen on the sly and I'm sorry if you thought
that; I seriously thought it wasn't going to be an issue. But since it
is for some I promise I won't make any
On 02/29/2016 12:09 PM, M.-A. Lemburg wrote:
This is the part about all this CoC talk I never understand. Why
on earth would someone change their regular behavior when
"at a meetup or conference that has not implemented a CoC" ?
Sadly, there are plenty of people who act wildly differently
On 02/29/2016 06:00 PM, Steven D'Aprano wrote:
I have worked in a team where managers would apply policy changes that
affected the entire team (including other managers) without a period of
consultation, and it is toxic behaviour. It breeds resentment and a
feeling of being pushed into the
On 03/06/2016 08:54 PM, Brett Cannon wrote:
I just finished doing what was necessary to make Davin a core dev, so
let's welcome our first new core dev of 2016!
Congratulations, Davin! Glad to have you. :)
--
~Ethan~
___
python-committers mailing
On 03/04/2016 03:07 PM, R. David Murray wrote:
> I guess I have one more thing to say.
[snip]
> [*] I think it is a feeling of annoyance, like I'm being nagged for
> no good reason [...]
I'm inclined to agree, but some bureaucracy is the price of success. Be
grateful somebody else is
On 03/04/2016 04:07 PM, Brett Cannon wrote:
We also still have no female or minority members.
Well, I'n not female, but I am of Native American / Latino descent. So
you have at least one. :)
And yes, those extremely low numbers of new committers are a bit
worrying. :(
--
~Ethan~
On 07/26/2016 07:32 AM, Nick Coghlan wrote:
On 26 July 2016 at 21:22, Victor Stinner wrote:
It looks like the Android port is also related to cross-compilation,
so it looks like CPython 3.6 will be easier to cross-compile as well.
Great!
For Android, the HQ is the "Meta-issue: support of the
On 01/30/2017 03:10 PM, Mariatta Wijaya wrote:
Looking forward contributing more and working with everyone here :)
Welcome and congratulations!
--
~Ethan~
___
python-committers mailing list
python-committers@python.org
On 02/10/2017 07:55 AM, Brett Cannon wrote:
Assume you can't commit to Mercurial anymore and the next email from me
will either be an introduction email to our new workflow or me apologizing
for something going horribly wrong. Either way I'm hoping you will hear
from me later today. :)
Welcome, Inada-san!
Glad to have you on the team.
--
~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/
On 04/01/2017 02:16 AM, Paul Moore wrote:
On 1 April 2017 at 09:17, Antoine Pitrou wrote:
But even if that *is* the case, there
comes a point where treating all participants equally does mean we're
OK to say "sorry, you're being unproductive and that won't change, so
we can't work with you"
On 04/26/2017 10:35 PM, Terry Reedy wrote:
On 4/26/2017 1:45 PM, Brett Cannon wrote:
:) But they are at least executed which is what we're really measuring here and
I think all Ethan and I are advocating
for.
I thought Ethan was advocating for more -- a specific unittest for each line.
On 04/21/2017 03:29 PM, Victor Stinner wrote:
I dislike code coverage because there is a temptation to write artficial tests
whereas the code is tested indirectly or
the code is not important enough to *require* tests.
If it's not important enough to require tests it's not important enough
On 05/01/2017 03:32 PM, Christian Heimes wrote:
With Github I'm seeing a major paradigm shift. New contributors tend to
use BPO as ticket number dispenser. Actual discussion seems to happen
mostly on Github PRs. For me it makes it harder to follow discussion
> [...]
I don't have any answers,
On 05/23/2017 11:15 AM, Brett Cannon wrote:
While at the PyCon US sprints the idea came up of offering Carol Willing
developer privileges
I've always been impressed with her interactions.
+1
--
~Ethan~
___
python-committers mailing list
On 06/14/2017 02:07 PM, Donald Stufft wrote:
I’m +1 on reverting the change, I’d even go so far to say I’d be +1 on doing it
as a first response. It’s always
possible to revert the revert once the person who committed the patch has time
to investigate the failure and recommit
the patch with a
On 12/05/2017 05:00 PM, Guido van Rossum wrote:
I'd like to propose Ivan Levkivskyi as a new core committer.
I thought he already was one.
+1 to bring him in!
--
~Ethan~
___
python-committers mailing list
python-committers@python.org
On 12/06/2017 04:48 PM, Victor Stinner wrote:
I propose to promote Julien Palard as a core developer.
I know that Julien doesn't have the typical profile of core
developers, only or mostly contribute to the code: Julien is currently
focused on the doculmentation.
Good documentation is
On 12/07/2017 10:01 AM, Victor Stinner wrote:
Note: I'm trying to avoid gender to be inclusive when mentioning a
contributor by using "they" or "their". I'm not sure that it's correct
in english, since english is not my first language. Is "they"
acceptable to identify a single contributor, or
Ivan,
Welcome! Glad to have you!
--
~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/
On 12/06/2017 09:43 AM, Victor Stinner wrote:
Congrats Cheryl!
Possibly a dumb question, but is Cheryl on this list?
--
~Ethan~
___
python-committers mailing list
python-committers@python.org
On 05/14/2018 01:41 PM, Larry Hastings wrote:
Dr. Mark Shannon contributed the "key sharing dictionary" to Python, writing
both the PEP and the implementation. This
shipped in Python 3.3 and was listed as one of the top features of that release as
according to the "What's New?" document.
With Tim's and Guido's latest suggestions,
+1
--
~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/
On 05/22/2018 06:06 PM, Steven D'Aprano wrote:
On Tue, May 22, 2018 at 05:58:39PM -0400, Donald Stufft wrote:
On May 22, 2018, at 5:50 PM, Victor Stinner wrote:
One of the problems with PEP 572 was that the discussion was fractured
across multiple threads on two mailing lists, leading to the
On 06/19/2018 11:17 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 not shown any sign of activity (on the
>> b.p.o. or GitHub,
On 06/19/2018 11:14 AM, M.-A. Lemburg wrote:
Ok, let me be even clearer :-)
While I understand that there is a need to show the world that
we need more active core devs, this drive to shelve existing
developers is not a good way to achieve this.
Here's a simple approach which is effective
On 06/02/2018 12:46 PM, Mariatta Wijaya wrote:
And perhaps this is to be discussed in a separate thread: even though in the
b.p.o we appear to have 170 committers,
really there are 90 core devs (people who has commit right to CPython on
GitHub). and out of those 90, I think only
about half
On 01/20/2018 11:19 AM, Jesus Cea wrote:
I plan to come back to python development (about time!) but I truly
hates git. I am experimenting with mercurial + hg-git extension and it
is quite usable (after the initial painfully slow clone time), but I am
having small quirks that I would like to
I created a new pull request to add a forgotten news entry, and now it's going
through all the pre-checks, etc.
I seem to recall we could add a "trivial" tag to an issue to skip those. Is
that still true, and if so, how?
--
~Ethan~
___
On 01/26/2018 12:45 AM, Terry Reedy wrote:
On 1/26/2018 1:28 AM, Ethan Furman wrote:
I created a new pull request to add a forgotten news entry, and now it's going
through all the pre-checks, etc.
I seem to recall we could add a "trivial" tag to an issue to skip those. Is
that
On 01/24/2018 03:23 PM, Yury Selivanov wrote:
I want to propose granting commit privileges to Nathaniel J. Smith.
I also thought he was already. Definitely +1 !
--
~Ethan~
___
python-committers mailing list
python-committers@python.org
On 01/26/2018 01:09 PM, Ned Deily wrote:
On Jan 26, 2018, at 16:05, Ethan Furman <et...@stoneleaf.us> wrote:
On 01/26/2018 09:28 AM, Mariatta Wijaya wrote:
So when the original PR didn't have a news entry, what should I have seen
to alert me to that?
If a news entry is missin
On 01/26/2018 09:28 AM, Mariatta Wijaya wrote:
So when the original PR didn't have a news entry, what should I have seen
to alert me to that?
If a news entry is missing from the PR, the CI check at the bottom of the PR
will fail.
You should see the following:
bedevere/news -- No news
Welcome!! I remember how excited I was to be offered a core-dev position. It
really is a cool thing.
On 06/20/2018 08:30 AM, Pablo Galindo Salgado wrote:
Thank you everyone for you support and for your work improving Python and the
Python community!
Thank you for be willing to join in
On 07/18/2018 08:45 PM, Łukasz Langa wrote:>
>> On Jul 18, 2018, at 9:36 PM, Nathaniel Smith wrote:
>>
>> I propose: no governance decisions finalized before October
>> 1, 2018.
>
> +1 but it's okay and expected that discussions here will continue in the
interim.
Absolutely! Without
On 07/19/2018 04:47 PM, Victor Stinner wrote:
or: Replace Dictatorship with Democracy.
Hi,
== Introduction: unjustified fears? ==
I see that many people are eager to replace the old governance based
on a single BDFL with a new governance with a new BD(FL) and/or a
council. My problem is that
On 07/18/2018 01:43 AM, Antoine Pitrou wrote:
Le 18/07/2018 à 04:02, Barry Warsaw a écrit :
If you’ve read this far - thank you! Now for the big reveal. I think the
>> Next BDFL should be… (drum roll)…
Brett Cannon
Since you're opening this can of worms, I'll say it:
- I'm -1 on a new
On 07/18/2018 09:36 AM, Łukasz Langa wrote:
On Jul 18, 2018, at 10:58 AM, Ethan Furman wrote:
If we, by majority vote, pick a governance model (dictator, council, or
>> whatever), then that legitimizes it. If we, by majority vote, pick the
>> new BDFL, then that legitimize
On 07/18/2018 03:04 AM, Antoine Pitrou wrote:
Hi Ethan,
Le 18/07/2018 à 11:49, Ethan Furman a écrit :
You're creating a huge problem here. Whatever dictator you come up
with, not everyone will be ok with that choice. What are they supposed
to do? If one doesn't think X is legitimate
On 07/18/2018 09:40 PM, Carol Willing wrote:
I am in favor of a time limit. Yet, October 1 seems a bit too long for the
initial governance decision (i.e. how to
decide how to decide). My perspective, based on transitions in non-profits and
the corporate world, is that the longer
an
On 07/17/2018 07:02 PM, Barry Warsaw wrote:
TL;DR: I propose keeping a singular BDFL and adding a Council of Advisors
> that helps the BDFL in various capacities, with additional responsibilities.
Having a singular BDFL certainly has its advantages, and from my interactions with Brett I
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
On 07/12/2018 12:28 PM, Barry Warsaw wrote:
On Jul 12, 2018, at 12:16, Brett Cannon wrote:
Maybe another way to label this is design stewards? We seem to be
>> suggesting a cabal of folks who steward the overall design while
>> relying on experts as appropriate to handle finer details.
I
Guido,
Thank you for creating Python.
Thank you for giving me a second chance when I mouthed off to you.
Thank you for trusting us enough to leave this great project in our hands.
Thank you.
--
~Ethan~
___
python-committers mailing list
On 07/13/2018 11:21 AM, Ethan Furman wrote:
[...]
Sorry, was trying to generate a new thread. Please respond to that one instead.
--
~Ethan~
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo
On 07/12/2018 01:27 PM, Raymond Hettinger wrote:
For the bigger decisions (and there aren't many coming up), I have some
> suggestions on ways to improve the discussions so that the interested
> parties can have a more equal say in the outcome and so that the
> discussions can be more time
On 07/12/2018 01:27 PM, Raymond Hettinger wrote:
> For the bigger decisions (and there aren't many coming up), I have some
> suggestions on ways to improve the discussions so that the interested
> parties can have a more equal say in the outcome and so that the
> discussions can be more time
On 04/23/2018 07:39 AM, Nick Coghlan wrote:
With my recent proposal to accept Petr Viktorin as a specialist core
developer focusing on extension module imports receiving several +1's
and no concerns being raised,
Where did this conversation take place? I see no record of it here nor on the
On 04/23/2018 09:37 AM, Christian Heimes wrote:> On 2018-04-23 17:43, Ethan
Furman wrote:
>> On 04/23/2018 07:39 AM, Nick Coghlan wrote:
>>> With my recent proposal to accept Petr Viktorin as a specialist core
>>> developer focusing on extension module imp
On 10/15/2018 09:22 PM, Benjamin Peterson wrote:
> Brett is exactly right about me. I'm following along on Discourse and
> this mailing list when I have the time. I plan to read the governance
> PEPs and vote when the time comes. But, I don't have anything useful
> to say.
>
> At the sprint, I
On 11/03/2018 03:55 AM, Paul Moore wrote:
Frankly, I feel pretty disenfranchised by the process
at the moment.
+1
--
~Ethan~
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
On 11/03/2018 11:45 AM, Donald Stufft wrote:
I would agree *if* that was the only axis that the two tools differed
on.
It's enough for me. My participation on Discourse is going to be so low
you might think I went emeritus. :/
(Un)fortunately there is a laundry list of improvements over
On 11/03/2018 12:32 PM, Donald Stufft wrote:
I don’t mean to suggest that my participation is make or break for these
lists. If I was the only one who felt this way, then I think it would be
fair to say that I’m in the minority and while we want to encourage
everyone, we can’t please
On 09/20/2018 05:47 PM, Brett Cannon wrote:
Which is why I'm hoping we can eventually get a clear enforcement guide written
for all the mailing lists and then have
a specific group of people manage all of these incident reports and deciding
how to handle them for consistency.
Otherwise we
On 09/20/2018 02:17 PM, Brett Cannon wrote:
I will also say I didn't voice an opinion or participate in the discussion on
the conduct WG when deciding how to handle
it (beyond outlining our levels of escalation when handling these situations).
One thing missing from the ban notification is
On 09/20/2018 05:06 PM, Nathaniel Smith wrote:
On Thu, Sep 20, 2018 at 3:35 PM, Ethan Furman wrote:
And I have to argue against his use of the n-word* as being part of the
reason -- he wasn't calling anybody that, he was using the word as an
example of a taboo in one culture
On 09/21/2018 07:51 AM, Antoine Pitrou wrote:
Le 21/09/2018 à 14:45, Paul Moore a écrit :
It's not likely to be a practical option on a mailing list, but in
primary school (which the whole conversation felt like) a likely
response would have been to put *everyone* involved in a time-out for
a
On 09/14/2018 12:28 PM, Raymond Hettinger wrote:
At the developer sprints this week, we collectively decided to grant core
committer status to Emily and Lisa.
Please join me in welcoming them to the team.
Woohoo!!! I thought you two were already core-devs -- I'm happy to see
it is now so!
Thanks, Brett.
--
~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/
Greetings!
I have a non-core dev willing to help maintain the cgi/cgitb modules along with
myself.
Would this consist of adding the both of us as experts on those modules, and
then I would be responsible for the mechanics of approving/merging any PRs?
Assuming this individual does well we
On 12/03/2019 07:27 AM, Lars Gustäbel wrote:
My name is Lars Gustäbel. I am the author of the tarfile module, and I have
been its maintainer for over ten years. I have not been active in the
bugtracker for a long time now, and I don't see that this will change in the
future. There are many open
On 12/10/2019 02:57 PM, Nick Coghlan wrote:
On Wed, 11 Dec 2019 at 06:52, M.-A. Lemburg wrote:
The conversion to an inactive dev is something that core devs need
to be asked to agree to, and thus needs to be managed as a status
flag, not depend on commits to the repo.
All committers were
On 02/11/2020 04:04 PM, Mariatta wrote:
On Tue, Feb 11, 2020 at 3:49 PM Ethan Furman wrote:
I'm trying to get the 3.3 and 3.4 branches so I can check my libraries'
compatibility with older versions, but I do not see those branches as being
available:
How can I get those?
3.3 and 3.4
Howdy!
I'm trying to get the 3.3 and 3.4 branches so I can check my libraries
compatibility with older versions, but I do not see those branches as being
available:
$ git branch --remote 89
remotes/upstream/2.7
remotes/upstream/3.5
remotes/upstream/3.6
remotes/upstream/3.7
Welcome! :-)
--
~Ethan~
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
On 05/01/2020 09:58 AM, Mariatta wrote:
Just wanted to share that the first 7 of 11 blog posts about presentations and
discussions from Python Language Summit are now up for your enjoyment.
Thanks!
--
~Ethan~
___
python-committers mailing list --
On 10/8/20 1:19 AM, M.-A. Lemburg wrote:
On 08.10.2020 00:26, Ethan Furman wrote:
On 10/7/20 2:47 PM, Antoine Pitrou wrote:
Apparently, Stefan Krah (core developer and author of the C _decimal
module) was silently banned or moderated from posting to python.org
mailing-lists.
This seems odd
On 10/8/20 4:07 PM, Thomas Wouters wrote:
> Stefan did indeed receive, and was notified of, a 1-year ban from core
development.
Thank you for clarifying.
> This action was based on advice from the Conduct WG and our own
deliberations. We
> wanted to have a discussion with him before we made
On 10/18/20 1:18 PM, Ned Deily wrote:
On Oct 18, 2020, at 15:45, Carol Willing wrote:
We've largely moved away from Travis for Jupyter testing in favor of Azure
pipelines and CircleCI as Travis was becoming increasingly slow and timing out.
Along those lines, if we are basically going to
On 10/7/20 2:47 PM, Antoine Pitrou wrote:
Apparently, Stefan Krah (core developer and author of the C _decimal
module) was silently banned or moderated from posting to python.org
mailing-lists.
This seems odd -- does the Steering Council care to comment?
--
~Ethan~
Congratulations, Brandt!
--
~Ethan~
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message
When a PR is merged, is it closed automatically or do we need to do something
to close it?
--
~Ethan~
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
Welcome, Lysandros!
Great to have you as part of the team!
--
~Ethan~
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
On 11/30/20 10:38 AM, Ernest W. Durbin III wrote:
All core devs should review
https://www.python.org/dev/peps/pep-8102/#active-python-core-developers
Roll not yet finalized
--
~Ethan~
___
python-committers mailing list --
On 11/30/20 11:01 AM, Mariatta wrote:
I think the PEP page hasn't been built yet to reflect the latest change.
It's in place now.
--
~Ethan~
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to
Greetings!
It seems I am unable to create PRs for 3.9. I've tried opening one directly,
and I've tried using the needs-backport label.
Any ideas what I'm doing wrong?
--
~Ethan~
___
python-committers mailing list -- python-committers@python.org
To
1 - 100 of 124 matches
Mail list logo
