On 7/3/23 12:15, Brett Cannon wrote:
> So, do people find this list useful enough to keep around, or should we
archive it?
Let's archive it.
--
~Ethan~
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to
Is this still scheduled for Thursday?
--
~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/
M
On 5/2/22 16:00, Jelle Zijlstra wrote:
We have added several new triagers today:
Do triagers have access to this list?
Regardless, congratulations!!
--
~Ethan~
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send a
On 4/6/22 11:48, Brett Cannon wrote:
Last chance on whether my tier 3 proposal make sense!
+1 for Brett's Tier 3 proposal. :-)
--
~Ethan~
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-comm
On 3/22/22 16:26, Brett Cannon wrote:
> [...] after discussing things we have three proposals:
>
> 1. Update PEP 2 to say a PEP is necessary to add a module to the stdlib
> 2. Update PEP 4 to say that a PEP is necessary to deprecate/remove a module
> 3. Mark PEP 411 as obsolete and thus droppi
On 2/17/22 10:47 AM, Senthil Kumaran wrote:
> If the utility value of the list has faded way, archiving the list, and
pointing the subgroup to
> other active places seems like better idea to me.
The list is useful, just for a very small set of people -- namely, those that want to contribute but
On 2/17/22 10:11 AM, Gregory P. Smith wrote:
>> - Subscriptions may expire for lack of activity, but resubscribing is
welcomed.
>
> This does not mean we /need/ to expel people due to inactivity. Lurking is
one method of learning.
And for that we have -list, -ideas, and -dev
> If we do want
Accidentally trimmed footnote with link to list info page, so reproducing the
page itself here:
> Summary
>
> Python Core Development Mentorship
>
> The Python Core Development Mentorship list is intended to provide a
welcoming introductory
> environment for developers interested in contributin
On 2/17/22 8:44 AM, Petr Viktorin wrote:
> On Mon, Feb 14, 2022 at 4:16 AM Ethan Furman wrote:
>> I'm looking to prune the core-mentorship subscriber list as I'm confident
90%+ are folks that
>> wanted help learning Python, not folks wanting help to develop Python
its
On 2/13/22 9:46 PM, Benjamin Peterson wrote:
> Does https://github.com/python/voters/ suffice?
That will get me the core-devs, but not the triagers. I will start with that, thanks. Ah, and I see we have a Python
Triage team on github as well; that's a small enough list I can add them by hand.
Greetings!
Is there a list somewhere of the core developers and triagers?
I'm looking to prune the core-mentorship subscriber list as I'm confident 90%+ are folks that wanted help learning
Python, not folks wanting help to develop Python itself. Towards that end I want to unsubscribe anyone wh
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
https://m
On 7/12/21 8:42 AM, Ewa Jodlowska wrote:
> Just to circle back, we have officially contracted with Łukasz Langa to be
the first CPython Developer-in-Residence!
Congratulations, Łukasz!
--
~Ethan~
___
python-committers mailing list -- python-committer
On 5/14/21 3:28 AM, Victor Stinner wrote:
> I'm always connected to IRC #python-dev (Freenode) for 10 years, a few
> other core devs use it time to time. Come to say hello ;-)
I've tried the IRC channel -- way too much noise. Talking to bots is not my
idea of a python dev chat.
My impression
Congratulations and 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 ar
On 3/31/21 7:29 AM, Ethan Furman wrote:
Also note that the tests pass fine locally, suggesting that this is a CI
problem. [1]
I added (re)imports of Flag to those tests, and it's going through CI now.
--
~Ethan~
___
python-committers mailing
On 3/31/21 6:59 AM, M.-A. Lemburg wrote:
It seems that some of the doc tests are missing imports of
e.g. Flag from enum.
My understanding of doctest is that the global execution environment is
cumulative. For example. the three previous tests, which all pass, are also
not reimporting Flag.
On 3/31/21 3:52 AM, Mark Shannon wrote:
My PR tests are failing seemingly due to some bug in enum.rst
Which might be caused by https://github.com/python/cpython/pull/22392
(that's the superficial cause, it might not be the root cause).
As far as I can tell, it is not the root cause. I (and ot
On 2/8/21 3:02 PM, Nick Coghlan wrote:
> On Tue, 9 Feb 2021, 8:18 am Terry Reedy wrote:
>> The one thing I think needs to be discussed and not been much, at least
>> not publicly that I have seen, is whether we really want to go down the
>> road of contextual keywords. There are some negatives a
Greetings, all!
I was wondering if there was any movement on PEPs 634-636?
As Guido mentioned on another PEP, time is running out to get this into 3.10.
--
~Ethan~
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send
The question:
Can we change the name of classes if we keep the old name as an alias?
The specifics:
When Enum was first created for 3.4 I thought the name `EnumMeta` was
clever and appropriate. However, in the intervening years an error
message has occasionally popped up with mention of an
On 12/16/20 7:47 AM, raymond.hettin...@gmail.com wrote:
Congratulations.
Yup, congratulations all!
Now please hurry up and accept the pattern-matching PEPs. ;-)
--
~Ethan~
___
python-committers mailing list -- python-committers@python.org
To unsub
On 12/12/20 5:00 PM, Mariatta wrote:
I've deployed a fix in miss-islington (https://github.com/python/miss-islington/pull/421/files) so this should be
working again now.
I've retriggered backports to several PRs that were stuck.
Many thanks!
--
~Ethan~
___
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 u
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 python-co
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 -- python-committers@python.o
Congratulations and 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 ar
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 ign
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 t
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/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 archiv
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
https://mail.pyt
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
https://mail.python.org/mailman3/lists/python-co
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 -- p
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
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
remotes/up
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
http
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 ask
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
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 sh
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 everyone.
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 th
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
C
On 10/17/2018 03:05 PM, Victor Stinner wrote:
Oh, by the way, should we have two different choices: remove the
commit bit from a core dev (downgrade a core dev as a regular
contributor) and ban a core dev?
No. If it comes to this, then the dev needs to be banned. I would not
expect this to
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 ve
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/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 have
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 that is n
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 th
On 09/14/2018 02:02 PM, Zachary Ware wrote:
Most of my effort this week has gone into improving the state of
buildbot.python.org, which has largely gone into improving Buildbot
itself.
Excellent! Better tools are always welcome. Thank you!
--
~Ethan~
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/
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 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 organization
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 continuing
On 07/18/2018 07:36 PM, Nathaniel Smith wrote:
[tl;dr: We need some ground rules, because uncertainty makes it hard
to think straight. But if we get sucked into a complicated meta-debate
about the ground rules then that defeats the purpose. My proposal for
a Minimum Viable Ground Rule: let's all
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 legit
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 certai
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/13/2018 06:54 PM, Tim Peters wrote:
Or, short of that, by an approval vote of the Fellows (whatever it is we call
for-real PSF members these days).
Forgive my ignorance, but how does one become a PSF member?
--
~Ethan~
___
python-committers
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 effi
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 effi
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 li
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
python-commi
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 t
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 tha
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 with
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/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 are
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 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.
We'
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 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 imports receiv
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
Z
On 01/26/2018 01:09 PM, Ned Deily wrote:
On Jan 26, 2018, at 16:05, Ethan Furman 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 missing from the PR, the CI che
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 ent
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
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~
___
python-commit
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
https://mai
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 iron
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 is
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 hard.
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
https://mail.python.org/mailman/listinfo/python-committer
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
https://mail.
My apologies if this has been discussed/answered before, but is there a link from the github side to the bpo side? For
example, I'm looking at https://github.com/python/cpython/pull/2304 and it would be great if such a link existed to take
me directly to the bpo issue.
--
~Ethan~
_
On 06/16/2017 09:48 AM, Brett Cannon wrote:
Maybe we should amend PEP 11 to say that whomever volunteers to maintain a
platform
> must make sure that platform's buildbot is not red for longer than a month
[...]
How about three? Some life changes need more than a month to recover from... (de
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 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
python-com
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, b
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.
I'
On 04/25/2017 11:05 PM, Victor Stinner wrote:
On 04/25/2017 10:15 PM, INADA Naoki wrote:
`self.initfp()` is very unlikely raise exceptions. But MemoryError,
KeyboardInterrupt or
other rare exceptions may be happen.
unittest.mock helps a lot to test such corner case: mock initfp(
On 04/25/2017 10:15 PM, INADA Naoki wrote:
This is one examples I merged "untested line of code".
https://github.com/python/cpython/pull/162/files#diff-0ad86c44e7866421ecaa5ad2c0edb0e2R552
+file_object = builtins.open(f, 'wb')
+try:
+self.initfp(file_obje
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 to
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" re
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. :)
Eith
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
https://mail.python.org/mailma
1 - 100 of 149 matches
Mail list logo
