[python-committers] MSDN subscriptions/renewals
Hey all! It's everyone's favorite time of year: MSDN subscription season. Microsoft provides our team complimentary Microsoft Developer Network accounts, which gives us access to various Visual Studio versions, OS images, and a whole lot more in support of us developing and testing Python on Windows. *If you're interested, please read on and respond by Friday August 9.* In exchange for the following details, I'll submit our team's info as a batch and you should usually get an email about MSDN within a week. Sometimes the email goes to spam, and sometimes it doesn't get delivered at all. If yours is a renewal and you don't hear back, try logging in anyway next week. If it still doesn't work after a while, let me know and I'll ping our contact at Microsoft again and see if something went wrong. If you respond after Friday, that's fine, though it might take longer to process. *First Name:Last Name:* *Email Address:Complete Mailing Address:* Thanks for everyone's work! Brian ___ 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://mail.python.org/archives/list/python-committers@python.org/message/52SB4ZV6UGG4ODU4OESKCKTZNC4JE4JX/ Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Moderation of the Python community
On Wed, Oct 17, 2018 at 1:09 PM Donald Stufft wrote: > > > On Oct 17, 2018, at 11:34 AM, Brian Curtin wrote: > > I think this type of issue is better solved internally to our team, > perhaps via some form of mediator(s) I mentioned earlier, rather than > involving a wholly external group. Time is of course a finite resource in > open source, and people work is often/usually harder than code work, but I > think we do have some people around who care about the success of the > project to spend time mediating these kinds of conflicts so that we keep > everyone involved and solve whatever problem at hand in a satisfactory > manner. > > > Honestly, I think an independent group managing these issues is the right > way to handle them. I’m loathe to bring it up because the situation was a > long time ago, and has been resolved, but I’ve personally had to engage the > CoC process in regards to another core developers behavior. At the time the > way that was handled was contacting the PSF board, if the process was > instead to contact python-committers or something I likely would’t have > done it at all. I think it is important that if someone feels they’re > having a problem in a particular space, that they feel they have an > impartial and independent group of people to raise those concerns with. > Especially given who I've now found out is on that working group, I'm fine with them managing issues of behavior, but we should be able to (responsible for, even) handle standard team dynamics amongst ourselves. Maybe I was/am missing something, but I got the sense that Victor was describing something like technical discussions that get heated because two sides are passionate about their stance—a common and generally reasonable thing to occur—and that was where some people might find the distinction between conflict and misbehavior blurred. To me that's still a thing we should at least start to work on amongst ourselves, as opposed to something like the issues of offensive word choice or name calling. With the former we have some things to work on smoothing out towards a common goal, and the latter we just want none of. ___ 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] Moderation of the Python community
On Wed, Oct 17, 2018 at 8:04 AM Victor Stinner wrote: > Hi, > > I see more and more discussions about the moderation of the Python > community. > > There is a PSF "conduct" Working Group: > https://wiki.python.org/psf/ConductWG/Charter > > I noticed the following questions: > > * Lack of transparency on how moderation is decided > * Lack of transparency on the number of received Code of Conduct > incidents: maybe start to produce "Code of Conduct transparency > report"? (If such reports already exist, I'm sorry, I wasn't aware > :-)) > * Should the PSF conduct-WG handle conflicts between core developers? > > Would it be possible to write down rules to formalize the moderation? > Yes. For any medium applying a code of conduct there should be some guidelines applicable to said medium for how things are handled. To get this out of the way early, as the author of the current CoC, it intentionally doesn't prescribe any specific moderation because it depends on how and where it's applied given the people and tools available. Moderating Discourse might be different than moderating a mailing list which is different than a bug tracker. > For example: > > * First try to contact the author of an incident and warn them? Only > take an action immediately for exceptional cases like obvious spam? > * Maybe define numbers for ban: 1 week, then 3 months, then 6 months, > then 1 year? I would prefer to never ban someone forever. People can > change. > * Scope: does the moderationg apply to *any* public space? Or only to > a restricted list like: mailing lists and bug tracker? What about > Twitter and conferences? > For conferences, there are specific codes of conduct and applicable event handling guides that go with them, and I would just leave that area alone from this angle. I don't know that we should start meddling with conferences; leave that up to organizers who are dedicated to that and in several cases have actual training on this topic. Twitter can't even moderate itself, but I don't think that makes it anyone here's job. I would scope moderation to any spaces provided by or for this group, so tracker, mailing lists, GitHub, Discourse, and I think that's it? I don't really know if IRC and Zulip are still in play. * Should the incidents which occur in the private space be handled as > well? Bullying can occur in the private space. > We can't police everything, but I think handling private issues within the space of PSF resources (or whatever the governing body of what we're talking about is) is to be expected. For example, if I harass you via a private message on Discourse, that is a situation to be handled here. It doesn't need to go to everyone's inbox for it to be a problem we need to handle. I don't know that you can moderate other private things—private in the meaning of "PSF provided or not"—though. If I send you an inappropriate email just between you and I, that's between us and our email providers. I think it might be overstepping this group's bounds for you to say I can't use the bug tracker for a month due to something I did entirely outside of the scope of said group. It feels similar to some corporate policies, where if I'm inappropriate to you when I see you at the grocery store, that's not really the company's problem, but if I'm like that at our team dinner then it is a problem. There probably does exist some threshold where out-of-scope behavior crosses to where someone isn't welcome, but I don't know that it's generally quantifiable. That's probably something for a council or triad or working group to discuss on a case-by-case basis as it's above and beyond a reasonable range of behaviors that this group can have their eye on. * How to handle conflict between core developers? Not directly related > to the code of conduct. > If it's not CoC related conflict, do you mean conflict related to code, as in technical conflict over implementation details? I think we naturally have a few mediators in this case depending on the level of where it occurs. Release managers, delegates for PEPs, code area experts, and then I think there are a few who act in such a way due to longevity with the project. If we're looking for people to be specifically identified as mediators, we have a bunch of good ones around here. I'm not interested for work on such rules. I'm not sure neither if > it's the role of the Python core developers to propose something. > Maybe the PSF conduct WG should propose something, or even decide > directly? > Is anyone from this group on said working group? If not, I don't think they should be wholesale deciding guidelines for a group they're not a part of. They would seem to be a group of people we should work with as they've presumably come up with other guidelines and could be a useful set of people to help shape things. > Handling conflicts between core developers is the most difficult > question. I don't think that it's the role of the conduct working > group to handle t
Re: [python-committers] Python 4.0 or Python 3.10?
On Tue, Sep 25, 2018 at 2:38 PM Serhiy Storchaka wrote: > 25.09.18 22:40, Barry Warsaw пише: > > On Sep 25, 2018, at 15:31, Antoine Pitrou wrote: > >> So my preference would be on 3.10. > > 3.9 + 0.1 :) > > > > Renaming it to Python 4 is fraught with knock-on effects, so I think we > do reserve that for major changes. I doubt we’ll ever need for a > disruptive backward incompatible change *at the Python level* in a Python > 4, but I absolutely can see the possibility of incompatible changes at the > public C API layer. I’m not saying it *will* happen, but that’s what we > should reserve “Python 4” for if or when it happens. > > I concur. > > And changing the major version number itself is significant breaking > change. From the name of the executable (python3 vs python4) hardcoded > in Python and shell scripts to a number of third-party scripts that > contain in the best case: > > PY3 = sys.version_info[0] == 3 > if not PY3: > ... # implies Python 2 > > and in the worst case: > > PY3 = sys.version[0] == '3' > > Changing the minor version number from a single-digit to a two-digits > will break some software too, but I think that this breakage is smaller. > FWIW, we had a similar bump in 2015 (?) when 2.7.10 was about to come out. Moving up to two digits might break some assumptions, though users misusing things isn't really our problem. Someone out there is parsing `sys.version[:5]` or `platform.python_version()` instead of the alternatives that are better suited to getting specific parts of the version. ___ 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] MSDN Subscriptions/Renewals
Hey everyone, I've had a few people reach out to me recently (or not so recently; sorry about that) about renewals for their MSDN subscriptions. If yours is expired or soon to expire, please send me the email address you're using to login, your full name, and your mailing address, and after I've received a bunch of responses I'll send them over and you should get an email from Microsoft in a few days. NOTE: If you've contacted me in the last while and haven't received a response, please respond here. I'm sorry for leaving you hanging. If you've never had a subscription but would like one, please send me the email address you'll use as a login, your full name, and your mailing address. This will give you access to Microsoft's Developer Network, which includes access to things like Visual Studio and Windows licenses that we can use for working on Python. Thanks for everyone's work on Python! Brian ___ 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] Mentoring Office Hours - the idea, and a question
Yep, this is something I'm adding directly in the devguide so it's right where new contributors are already going to be looking for help and information. As for how those mentors and mentees actually do the work, to start with I think it's something that each person should just do what they're comfortable with and have access to, and then once we have some data to work off of, maybe then we prescribe some specific ways of doing it. I'm ok to do video things, but some might not be, so in getting this started I wanted to just begin with names, days, times, and contact information on an official website. If someone wants mentorship and they're available when I'm available, they reach out to me and we find a way to talk. On Wed, May 16, 2018 at 11:31 AM Victor Stinner wrote: > Hi, > > I'm usually available between 10:00 and 16:00 in the French timezone > (currently, it's CEST = UTC+2). > > A few months ago, I wrote a tutorial and a list of available core > developers... currently it's just me :-D > >http://cpython-core-tutorial.readthedocs.io/en/latest/getting_help.html > > Maybe this list should be moved in the developer guide? > >https://devguide.python.org/help/ > > I chose to put it in my tutorial, since it's less official, and I was > not sure if I should put myself in the official guide ;-) > > -- > > I also heard the idea of pair-programming using a chat, a video > conference, or something else. > > For example, when you work on a bug, do it with a contributor to show > how you work. I never did that before, but I may try ;-) > > Victor > > 2018-05-16 9:52 GMT-04:00 Brian Curtin : > > Hey all, > > > > At the Language Summit last week, after Mariatta's talk we had a > > conversation around diversity and how to grow our contributor base, which > > led to someone (Steve Dower?) suggesting we post a sort of "Office Hours" > > list. This would be a list of current core developers who are interested > in > > being available at set time(s) for helping mentor newer contributors in > our > > community through our process and, if they're interested, mentoring them > > through the process of becoming core developers themselves. > > > > This "Office Hours" concept is a type of thing that has worked well > > elsewhere, including around the software world, and we have some people > > interested in offering said mentorship, so I would like to move on to > > getting this list up somewhere so we can start doing it. > > > > With that said, before I go make a PR to the devguide to start iterating > on > > the implementation, an important question: > > > > As this is both an event similar to an in-person meetup and an event > meant > > to be a safe space for those getting started, it will explicitly mention > the > > code of conduct. As such, it needs a person/persons/list to contact > should > > something arise in this context that needs to be handled. What/who should > > that be? > > * Suggestion 1: use the already in-place > core-mentorship-ow...@python.org, > > though I can't tell who's on there. > > * Suggestion 2: Create some new list with a few key people on it. > > * Suggestion 3: List some direct names. Who? > > > > As for implementation, there are some tools out there we could possibly > use, > > but in the interests of getting something out there I'm just going to > make a > > table and fill in some common information, starting with my own. Calendar > > apps and other integrations can come as we figure them out. > > > > Brian > > > > ___ > > 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] Mentoring Office Hours - the idea, and a question
Hey all, At the Language Summit last week, after Mariatta's talk we had a conversation around diversity and how to grow our contributor base, which led to someone (Steve Dower?) suggesting we post a sort of "Office Hours" list. This would be a list of current core developers who are interested in being available at set time(s) for helping mentor newer contributors in our community through our process and, if they're interested, mentoring them through the process of becoming core developers themselves. This "Office Hours" concept is a type of thing that has worked well elsewhere, including around the software world, and we have some people interested in offering said mentorship, so I would like to move on to getting this list up somewhere so we can start doing it. With that said, before I go make a PR to the devguide to start iterating on the implementation, an important question: As this is both an event similar to an in-person meetup and an event meant to be a safe space for those getting started, it will explicitly mention the code of conduct. As such, it needs a person/persons/list to contact should something arise in this context that needs to be handled. What/who should that be? * Suggestion 1: use the already in-place core-mentorship-ow...@python.org, though I can't tell who's on there. * Suggestion 2: Create some new list with a few key people on it. * Suggestion 3: List some direct names. Who? As for implementation, there are some tools out there we could possibly use, but in the interests of getting something out there I'm just going to make a table and fill in some common information, starting with my own. Calendar apps and other integrations can come as we figure them out. Brian ___ 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] MSDN Subscriptions — First timers, renewals
Hey everyone, If you've been waiting on a recent subscription renewal, my apologies—I dropped the ball on following up on some of them, but I'm getting things back in order with another request for renewals now that a few more are flowing in. If you are currently expired or within a month or so of a renewal, please send me the email address you use, your full name, and your mailing address. We haven't always needed mailing address for renewals, but they have been asking for it lately. If your expiration is a few months away, they seem to prefer we don't get too far ahead so email me directly when that time comes, or perhaps another one of these batches will match up. If you've never had a subscription but would like one, please send me the email address you use, your full name, and your mailing address. This will give you access to Microsoft's Developer Network, which includes access to things like Visual Studio and Windows licenses that we can use for working on Python. Thanks for everyone's work on Python! Brian ___ 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] Windows License for a core dev
I think you're asking about an MSDN subscription, which gives you access to various Microsoft products including Windows, and yes you can have one. I just need the following details: First Name: Last Name: Email Address: Project/Company: Python Software Foundation Complete Mailing Address: Phone Number: As for VirtualBox on Mac, I have no idea, but probably? You can download ISOs from MSDN and I think that's all you need. Brian On Thu, Jun 8, 2017 at 12:39 PM, Mariatta Wijaya wrote: > Hi, > > During the language summit I overheard that as a core developer, I can get > free Windows License. Is this true? > If so, how can I get one, and will it work with VirtualBox on mac? > > Thanks. > > Mariatta Wijaya > > ___ > 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] Proposal for procedures regarding CoC actions
On Wed, May 3, 2017 at 3:28 PM, Mariatta Wijaya wrote: > Hi, > > First of all, sorry for bringing up an old thread. > I know this is an uncomfortable topic, and I also wish that we can just > avoid it, but ... I think we gotta do something about it. > > I understand why Brett did what he did, and I support his decision. > > I do agree with Raymond's point, that going forward, we should have > a procedure in place, we all need to know what the rules are, and how to > play by the rules. > > Communities like Django Project and Write The Docs have clear enforcement > manuals on what to do in case of CoC violation: > https://www.djangoproject.com/conduct/enforcement-manual/ > http://www.writethedocs.org/code-of-conduct-response/ > > Can we adopt something like that to our community, or do we have this > already? > If it requires involvement with the PSF board, who could bring this to > their attention? (I'm new I don't know how these things work yet) > It should not require PSF involvement. Enforcing violation of the CoC is up whichever group applied the CoC and how it factors into the medium it's being applied to, so I think we just do that right here. That's partly why the CoC itself says nothing about consequences, as the myriad of environments this could be (and is) applied to vary, so there is no one-size-fits-all answer to what happens when it's violated. ___ 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] Disable Codecov on GitHub pull requests?
On Mon, Feb 13, 2017 at 1:11 PM, Brett Cannon wrote: > > > On Mon, 13 Feb 2017 at 07:26 Victor Stinner > wrote: >> >> 2017-02-13 16:04 GMT+01:00 Donald Stufft : >> > I’ve also never see the random -0.01% >> > coverage of code in another project, and my guess is that there is some >> > sort >> > of non-determinism in the CPython test suite that would be a good idea >> > to >> > make deterministic anyways. >> >> Can we hide/disable Codecov notifications until this issue is fixed? >> Example of false alarm: >> https://github.com/python/cpython/pull/61#issuecomment-279291824 >> heapq.py coverage -0.77% on a change modifying Doc/library/typing.rst >> >> See also: "Adjust coverage failure threshold" >> https://github.com/python/core-workflow/issues/21 > > > Codecov's configuration is controlled by > https://github.com/python/cpython/blob/master/.codecov.yml so you can submit > a PR to propose changes to how coverage is reported. Docs can be found at > https://docs.codecov.io/docs/codecov-yaml . Berker has https://github.com/python/cpython/pull/71 up right now. I think it looks ok so far from what I understand. ___ 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] My cavalier and aggressive manner, API change and bugs introduced for basically zero benefit
I've been on the sidelines for a while myself for a number of reasons, but the shift to GitHub will pull me back in for sure, at least in terms of code review. I look forward to actually contributing code again soon, but easier tooling on reviews—rather, a shiny new one, as I'm aware of Reitveld—is enough of a carrot to bring me back in. On Sun, Jan 22, 2017 at 12:08 PM, Tal Einat wrote: > Dormant core dev here. Not contributing at all due to severe lack of > time in the past year and a half, not likely to have more time in the > near future. Also no longer working with Python at all except as a > hobby :( > > I could pull off a review once a month if it would actually help! > > On Sat, Jan 21, 2017 at 9:51 PM, Brett Cannon wrote: >> What I'm picking up from this is (as a gross oversimplification): >> >> * Victor _wants_ code reviews >> * Raymond thinks we _need_ code reviews >> >> So the common theme here regardless of whether you agree with Raymond or >> Victor's approach to development is that we are not getting enough code >> reviews to go around. To me that's what the systemic issue is that this >> email is bringing up. >> >> Now I think most of us don't think the solution to the lack of reviews is to >> lower our standard of what it takes to become a core developer (this doesn't >> mean we shouldn't do a better job of identifying potential candidates, just >> that we shouldn't give people commit privileges after a single patch like >> some projects do). To me that means we need to address why out of 79 core >> developers only 39 have a single commit over the past year, 30/79 have more >> than 12 commits over that same time scale, 15/79 people have more than 52 >> commits, and 2/79 people have over 365 commits >> (https://github.com/python/cpython/graphs/contributors?from=2016-01-22&to=2017-01-21&type=c >> for the stats). >> >> Some of you have said you're waiting for the GitHub migration before you >> start contributing again, which I can understand (I'm going to be sending an >> email with an update on that after this email to python-dev & >> core-workflow). But for those that have not told me that I don't know what >> it will take to get you involved again. For instance, not to pick on Andrew >> but he hasn't committed anything but he obviously still cares about the >> project. So what would it take to get Andrew to help review patches again so >> that the next time something involving random comes through he feels like >> taking a quick look? >> >> As I have said before, the reason I took on the GitHub migration is for us >> core developers. I want our workflow to be as easy as possible so that we >> can be as productive as possible. But the unspoken goal I have long-term is >> to get to the point that even dormant core devs want to contribute again, >> and to the point that everyone reviews a patch/month and more people >> reviewing a patch/week (although I'll take a patch/year to start). I want to >> get to the point that every person with commit privileges takes 30 minutes a >> month to help with reviews and that the majority of folks take 30 minutes a >> week to review (and please don't think this as a hard rule and if you don't >> the privileges go away, view this as an aspirational goal). Even if people >> who don't have time to review the kind of patches Victor is producing which >> triggered this thread, reviewing documentation patches can be done without >> deep knowledge of things and without taking much time. That way people who >> have time to review the bigger, more difficult patches can actually spend >> their time on those reviews and not worrying about patches fixing a spelling >> mistake or adding a new test to raise test coverage. >> >> All of this is so that I hope one day we get to the point where all patches >> require a review no matter who proposed the code change. Now I think we're >> quite a ways of from being there, but that's my moonshot goal for our >> workflow: that we have enough quality reviews coming in that we feel that >> even patches from fellow core developers is worth requiring the extra code >> check and disbursement of knowledge without feeling like a terrible drag on >> productivity. >> >> Once the GitHub migration has occurred I'm planning to tackle our Misc/NEWS >> problem and then automate Misc/ACKS. After that, though, I hope we can take >> the time to have a hard look at what in our workflow prevents people from >> making even occasional code reviews so that everyone wants to help out again >> (and if any of this interests you then please subscribe to core-workflow). >> >> >> On Fri, 20 Jan 2017 at 02:46 Victor Stinner >> wrote: >>> >>> Hi, >>> >>> Raymond Hettinger used a regression that I introduced in the builtin >>> sorted() function (in Python 3.6.0) to give me his feedback on my >>> FASTCALL work, but also on Argument Clinic. >>> >>> Context: http://bugs.python.org/issue29327#msg285848 >>> >>> Since the reported issues is wider than just FASTC
[python-committers] MSDN Subscriptions - first timers and renewals
Hey all, I heard some of you wanted MSDN subscription renewals from Santa Claus, so I can take care of that and put in a good word for you. If you're an existing subscriber I just need the email and subscriber ID for your account, which you can get out of some of the emails they send you, or via https://msdn.microsoft.com/en-us/subscriptions/manage/. If you don't have a subscription and would like access to various Microsoft tools to help you make Python better, e.g., Visual Studio, Windows images, etc., they give us complimentary access to the Microsoft Developer Network to enable that. Each subscription gets you one year of access to download those tools (plus some amount of Azure credit), and they give us continued renewals as long as we're using them and making Python better. If you'd like a subscription for the first time, I need the following info: First Name: Last Name: Email Address: Project/Company: Python Software Foundation Complete Mailing Address: Phone Number: I'd like to batch these up so it makes things easier on the folks at Microsoft who help us out with this, so get me your details and I'll send a batch next week on the 28th, and any batches after that I'll just gauge by how many are coming in. Thanks, Brian ___ 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] MSDN subscriptions/renewals
Hey all, The fine folks at Microsoft have been giving us complimentary access to Microsoft Developer Network subscriptions for many years now in support of Python on Windows, and it's soon going to be expiration time (or past that) for some of your accounts. If any existing subscribers anyone would like a renewal, please send me both your email login as well as your Subscriber ID. You can find that at https://msdn.microsoft.com/en-us/subscriptions/manage/ once you're logged in. If you would like a subscription for the first time, which gives you access to Visual Studio, Windows disk images, and more, please send me all of the following: First Name: Last Name: Email Address: Project/Company: Python Software Foundation Complete Mailing Address: Phone Number: In order to ease the work on our Microsoft contact's side, I'd like to batch up the list of names that we send them, so I'm going to collect responses for a week or so and then send them off. After that it takes around a week for them to go through it and get everything enabled, after which Microsoft will send you an email about your new subscription. Brian ___ 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] Making the PSF CoC apply to core developers
On Saturday, February 27, 2016, Stefan Krah wrote: > Brett Cannon python.org> writes: > > > I noticed that the devguide didn't explicitly mention that core > developers > were expected to follow the PSF CoC > (https://docs.python.org/devguide/coredev.html and > https://www.python.org/psf/codeofconduct/, respectively). I have > opened http://bugs.python.org/issue26446 to make sure it gets documented. > > Since this is technically a modification of the requirements of getting > commit privileges I wanted to mention it here before I (or anyone else) > made > the change. > > When I started here, the PSF and python-dev were considered disjoint > entities (quoting MvL from memory). Looking at > > https://www.python.org/psf/records/board/history/ , > > half of the current directors have never appeared anywhere on the > python-dev > infrastructure, most notably on python-checkins. > > Contrast this with e.g. the period of 2003-2004, where I still know all of > the directors even though I did not know Python at that time! > > Some very prolific contributors do not appear in the list of PSF members > at all. > > > This particular CoC specifically addresses conference misbehavior, which is > fine. FYI It has nothing to do with conferences. ___ 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] MSDN Subscription Expired
I'll double check - occasionally something gets tripped up with these. On Sun, Nov 29, 2015 at 3:28 PM, Ethan Furman wrote: > On 11/07/2015 06:57 AM, Brian Curtin wrote: > >> All I need is the email associated with the account and your >> Subscriber ID. > > I haven't heard anything yet, did I miss something? > > -- > ~Ethan~ ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] MSDN Subscription Expired
On Saturday, November 7, 2015, Ethan Furman wrote: > Woops. > > Can I get it renewed? > Does anyone else need a renewal? It's easier on the Microsoft end if I send them in a batch. All I need is the email associated with the account and your Subscriber ID. Brian ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers
[python-committers] MSDN subscriptions, Intel ICC licenses
It's that time again: a batch of MSDN subscriptions are expiring, and I've already heard from a few of you, so in order to make it easier on the Microsoft end, I'll put together another batch of us to be renewed all at once. If you would like a renewal, I need the email address associated with your account as well as your subscriber ID. You can find the ID in the top left of https://msdn.microsoft.com/en-us/subscriptions/manage If you would like a first time subscription, I need your postal address and the email address you'd like to use for the account. We also now have a contact at Intel who can provide our developers with licenses for Intel ICC compilers. I don't know exactly what information they're going to need from you, but let me know if this is something you'd like to make use of. Brian ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] [Python-Dev] Do we need to sign Windows files with GnuPG?
On Fri, Apr 3, 2015 at 7:25 AM, Paul Moore wrote: > On 3 April 2015 at 10:56, Larry Hastings wrote: >> My Windows development days are firmly behind me. So I don't really have an >> opinion here. So I put it to you, Windows Python developers: do you care >> about GnuPG signatures on Windows-specific files? Or do you not care? > > I don't have a very strong security background, so take my views with > a pinch of saly, but I see Authenticode as a way of being sure that > what I *run* is "OK". Whereas a GPG signature lets me check that the > content of a file is as intended. So there are benefits to both, and I > thing we should continue to provide GPG signatures. (Disclaimer: I've > never in my life actually *checked* a GPG signature for a file...) I haven't been on Windows in a bit, but this is my understanding/expectation as well. ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Proposing Paul Moore for commit privileges
On Sat, Mar 14, 2015 at 3:23 PM, Brett Cannon wrote: > Paul has been participating on python-dev for quite a while, he is a > committer on pip, and (co-)author on 5 PEPs. At this point I think it would > be prudent for Paul to have commit privileges if for any other reason than > to help manage the code related to his PEPs. But on top of that I bet Steve > wouldn't mind more help managing Windows-specific stuff. I'm out of date in terms of recent code contribution, but in the past Paul had always been very helpful, and I've seen his name a lot on python-dev especially recently. +1 for sure. ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] [Python-Dev] Minor update to Python 3.5 release schedule
On Sat, Mar 14, 2015 at 9:48 PM, Larry Hastings wrote: > > > I always intended all my releases to be on Sundays--that all the release > engineering work is done on weekends, which is generally easier for > everybody. But I goofed up the 3.5 release schedule and had proposed > 3.5.0a3 to be released Saturday March 28th. With the assent of the team I > bumped it forward a day to Sunday March 29th. I apologize for my goof. You're fired ...nah. Thanks for everything everyone has done for this release. ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] MSDN Subscriptions/Renewals
On Tue, Mar 3, 2015 at 11:13 AM, Trent Nelson wrote: > On Tue, Mar 03, 2015 at 10:27:34AM -0500, Yury Selivanov wrote: >> Hi Brian, >> >> My subscription expires today.. > > I think you get a grace period for a couple of weeks which is handy. Yep, usually there's some grace period. If anyone else is in need of a renewal, let me know. >> Is it possible to renew it somehow? > > So, I ended up renewing my subscription most recently via an online > form referenced in a private area for Apache committers. I'll send > the link in a private follow-up e-mail to you and Brian (and anyone > else if they'd like it). > > I'd paste it here but all the Apache docs indicate that the URL > shouldn't be made public, and this is a publicly-archived mailing > list, so... > > (Do we have a private area/wiki/repo for committer-eyes-only, out of > interest?) I would hazard against sending that around in case it's tied to Apache people, or something. In the past I've helped other people gain a connection to have MSDN support for their project (related to Python, but not CPython specifically, so I didn't feel safe handing out subscriptions to them), and they ended up being handled by different people or in different ways. ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers
[python-committers] MSDN Subscriptions/Renewals
Hey all, Since I've gotten a couple of requests now for MSDN renewals, I may as well try to do them in a big batch. If you have an MSDN subscription that is expired or soon expiring, I can get you a renewal if you send me the email address you use to login and your Subscriber ID. This is found at https://msdn.microsoft.com/subscriptions/manage/ If you don't have a subscription but would like one - it gives you access to Windows ISOs, Visual Studio, and other Microsoft software - please send me your preferred email address, mailing address, and telephone number, and I'll get you setup. Brian Curtin ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers
[python-committers] MSDN renewals
Hi all, I've been told there's a batch of MSDN subscriptions about to end soon, so if you're in that camp, please let me know if you'd like a renewal by giving the email address associated with your account as well as your subscription ID. You can find that ID at https://msdn.microsoft.com/subscriptions/manage/ when logged in. As usual, if you need a first time subscription, let me know your preferred email, mailing address, and phone number (they don't mail or call you, but they are required fields). Brian ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers
[python-committers] MSDN Renewals
Hi all, I've heard from some people in a previous batch that their MSDN subscriptions are due to expire in January. If yours will be expiring soon and you'd like an update, please let me know the email address associated with the account, and your subscription ID. I believe that ID was included in a notification email you might have gotten informing you of the upcoming expiration, but if not, you can find it on https://msdn.microsoft.com/subscriptions/manage/ when you're logged in. If you don't currently have a subscription (it gets you Visual Studio, OS licenses, etc) but would like one, please send me the email you'd like to use for the account, your mailing address, and your phone number. They don't mail you or call you, but Microsoft requires that info for the subscription. Brian ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] PyCon Language Summit: Wednesday 9th April
On Wed, Dec 4, 2013 at 2:47 PM, M.-A. Lemburg wrote: > On 04.12.2013 21:28, Eli Bendersky wrote: > > On Wed, Dec 4, 2013 at 11:47 AM, M.-A. Lemburg wrote: > > > >> On 04.12.2013 20:07, Benjamin Peterson wrote: > >>> 2013/12/4 Barry Warsaw : > On Dec 04, 2013, at 07:15 PM, Antoine Pitrou wrote: > > > As for the question, I think we should wait at least two or three > years > > before "sunsetting" 2.7. > > I've been thinking we should move Python 2.7 to security-fix only > >> around the > Python 3.5 time frame, with a couple more years of promised security > >> support. > >>> > >>> FWIW, the current plan is to have the last normal release in 2015 and > >>> security releases "indefinitely" (2020 or something like that). > >> > >> Just as data point: we have customers that still request Python 2.4 > >> compatible versions of our products - simply because they cannot > >> upgrade. The last release of that series was in 2008. > >> > > > > I was always curious about these "cannot upgrade" cases. Most of the > time, > > they seem to boil down to "because that's the default Python our RHEL > comes > > with", completely ignoring the possiblity of just building a newer Python > > locally and/or carrying along with the product. > > > > Can you clarify on some specific interesting cases you ran into? > > One example is users stuck on e.g. Zope 2.10 or Plone 3.3 (or even > earlier). They cannot upgrade because they are using customized > installations and don't have the knowledge or resources to upgrade > the systems to later versions. Writing intentionally unmaintainable software and being locked into it is a different issue than platforms providing long-dead Python versions. If you do bad things, you're going to have a bad time. ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Anatoly has been warned about his behaviour potentially leading to his loss of tracker privileges
On Fri, Nov 29, 2013 at 12:22 PM, Tim Peters wrote: > I pretty much ignore Anatoly, and that works really well for me - try it > ;-) I've filtered his emails to the trash for close to two years now so I'm only aware of him when issues like this come up. He doesn't get to come in here and act how he does, and openly say he's being disrespectful on purpose, and then say that he can't be nice if we don't make him happy. I doubt he would walk into a restaurant, complain about the process they used to create their menu, then complain when they don't make food the way he likes, then be mean to the waiters and waitresses because they're not seeing to it that he is comforted. If he did, they'd just call the police and he'd be escorted out. ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Anatoly Techtonik's contribution (again)
On Fri, Nov 29, 2013 at 9:07 AM, Antoine Pitrou wrote: > > Hello, > > I'm a bit curious, but do people think Anatoly is now behaving more > constructively than before? He does seem to post *less*, otherwise... > > After all, he's just sent another rant about the "community process" in > which the word CLA seems to appear multiple times: > https://mail.python.org/pipermail/python-dev/2013-November/130632.html Saying that he's actively disrespectful because he doesn't agree, and then saying he can't be nice if he's not made to feel happy may be constructive to him personally, but not to the project. As he's done in the past several times, he wants changes, he wants his changes, and he's going to act this way if he doesn't get them. I used to do this when I was a child and didn't get to eat candy. ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers
[python-committers] Zachary Ware for commit access?
Hi all, What do you think about giving commit access to Zachary Ware? He's been active on the tracker for a while and has contributed a good bit of Windows code. I'm not doing much Windows stuff these days, and unfortunately I haven't had much time to contribute much lately. The latter will be changing, but the former probably won't. Anyways, Zach is interested in picking up some of our Windows slack and I think he could benefit from commit access. Although I've been mostly quiet, I have been nosy on most of his issues and have looked over most of the patches. I volunteer to continue looking after him as I too get back into contributing. Any thoughts? ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers
[python-committers] MSDN Subscriptions/Renewals
Hi all, Since I've gotten a handful of requests lately, I wanted to put out a call to try and handle them in a batch. That'll make it easier for the people at Microsoft who run their Open Source program. If you're using your MSDN subscription and it will be expiring in the next couple of months, go to https://msdn.microsoft.com/subscriptions/manage/ and send me the email address associated with the account, and the Subscriber ID. If you don't have an MSDN subscription but you would like a complimentary one, which gives you access to Windows ISOs/licenses, Visual Studio licenses, etc., please send me your preferred email, your mailing address, and a phone number. They don't mail you or call you, but those are required fields in their signup. I'm going to wait a few days, then send everything to Microsoft. After that, it usually takes a day or so for them to get to it and push our applications through. Once it's processed, you'll receive emails a few days later from msdntnord...@arvatousa.com saying the account is created and will soon be active, and then one from msubs...@microsoft.com with a link to activate it. Some people have had these go into spam folders, so keep an eye out for them. Thanks, Brian ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Interview with Coverity
On Wed, Jul 17, 2013 at 6:55 PM, Christian Heimes wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hello, > > Kristin Brennan from Coverity has asked me for an interview about > Python core development and how we are using Coverity Scan. Coverity > is planing to have a monthly series of interviews with open source > projects that use their service, for example > http://www.coverity.com/company/press-releases/read/coverity-introduces-monthly-spotlight-series-for-coverity-scan-open-source-projects > > She has send me a list of questions up front. I like you to review and > comment on my preliminary answers, please. > > Thanks, > Christian > > > Q: How many active developers do you have contributing to the project? > > - - 174 according to http://hg.python.org/committers.txt > > - - 152 according to > http://bugs.python.org/user?iscommitter=1&@action=search&@sort=username&@pagesize=300 > > - - about 60 active according to https://www.ohloh.net/p/python/ > > - - about 360 contributors agreements (513 - 152) according to > http://bugs.python.org/user?contrib_form=yes&%40action=search > > - - about 1400 names in Misc/ACKS I would simplify and say something like this: Of the project's 174 committers, around 60 are recently active, with contributions coming from many others. Perhaps try to figure out how many names were added to ACKS within the last year, then double it to get an estimate of non-committers who are active? ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] echosign
On Mon, Mar 4, 2013 at 9:43 AM, Antoine Pitrou wrote: >> I applaud the foundation for getting an electronic signature method in >> place. >> >> However, I have to say that to my mind echosign is nothing more than >> "authentication theater", and I wonder if it is going to make us look >> more than a bit clueless to the tech community. I'm surprised that >> a lawyer would consider a "signature" generated from typed text to be >> useful for anything. If you are are going to accept the typed signature, >> just accept the typed signature. > > I don't know what this is talking about. Is there an announcement somewhere I > missed? Or has the PSF declared announcements to be old-fashionable and > despicable? Sorry I didn't send the email at the exact same time as the blog posts that I had scheduled. You'll find out what we're talking about in some form or fashion at some point today. ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] MSDN subscriptions - new or renew
On Fri, Dec 28, 2012 at 10:41 AM, Brian Curtin wrote: > Hi all, > > Before we begin: please respond directly to me. > > I've gotten a few requests for MSDN subscription renewals, so I may as > well do a big call out to try and do this as a big group to make it > easier on MS. If you're due/overdue for a renewal, send me the email > address you use to login and the Subscriber ID -- this is found at > https://msdn.microsoft.com/subscriptions/manage/ when you're logged > in. > > If you do not currently have an MSDN subscription but are interested, > Microsoft's Open Source Technology Center provides our contributors > with free MSDN subscriptions to allow you to get OS and Visual Studio > installers/licenses. Please provide the following information if > you're interested: > > First Name: > Last Name: > Email Address: > Project/Company: Python Software Foundation > Complete Mailing Address: > Phone Number: > > > Since the Microsoft employee who helps us with this is unlikely to > respond right away due to the holidays, I'm going to gather up details > and send them on 2 January, 2013. > > After he responds, it typically takes one week before you receive login > details. > > Brian FYI: I heard back from Microsoft that they've processed all of the requests. Keep an eye on your spam folder as some people have seen the account details end up there. It usually takes a week or so for you to receive your details. Let me know too long goes by without receiving anything and I'll look into it. ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Anatoly Techtonik's contribution
On Tue, Jan 1, 2013 at 3:49 PM, Ezio Melotti wrote: > Hi, > > On Tue, Jan 1, 2013 at 10:57 PM, Georg Brandl wrote: >> On 01/01/2013 05:54 PM, Ezio Melotti wrote: >> >>> I say Ezio lets him know that this is the plan since he talked to him >>> recently and is in the no-ban-yet camp. >>> >>> >>> Yesterday I talked to him, informed him about the probation and showed him >>> this >>> message. I hope this is official enough. >> >> So, what was the reaction? That is the important thing to know... >> > > He acknowledged the fact, but I think he had already understood the > issue from our previous conversation. ...and? Does he care about what was said? Is he going to do anything about his actions? The fact that this discussion sidetracked into contributor agreements is not a good sign to me. He should have just said those things himself to the PSF's legal counsel, not in response to an email about his behavior... ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Anatoly Techtonik's contribution
On Fri, Dec 28, 2012 at 4:15 PM, John Benediktsson wrote: > I would caution against using hypothetical "new people" (that maybe possibly > could be offended in some way that might create harm either to that person or > the community) as a reason for taking this action. Does anyone know if this > has actually occurred? And in any significant numbers? > > I see a group of hard working core developers that are frustrated quite > legitimately and struggling with policing the content of official message > boards, but that energy might push you in directions that are more harmful > than not. > > Be sure of who you are acting against, the person more than the emails. > There is strong incidence of mental illness in the tech community and there > are also persons with significantly different email personalities than actual > personality. I didn't actually "meet" him so to speak, he just spoke at me and a group of others...so it was no different than what typically occurred via email/tracker. ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
[python-committers] MSDN subscriptions - new or renew
Hi all, Before we begin: please respond directly to me. I've gotten a few requests for MSDN subscription renewals, so I may as well do a big call out to try and do this as a big group to make it easier on MS. If you're due/overdue for a renewal, send me the email address you use to login and the Subscriber ID -- this is found at https://msdn.microsoft.com/subscriptions/manage/ when you're logged in. If you do not currently have an MSDN subscription but are interested, Microsoft's Open Source Technology Center provides our contributors with free MSDN subscriptions to allow you to get OS and Visual Studio installers/licenses. Please provide the following information if you're interested: First Name: Last Name: Email Address: Project/Company: Python Software Foundation Complete Mailing Address: Phone Number: Since the Microsoft employee who helps us with this is unlikely to respond right away due to the holidays, I'm going to gather up details and send them on 2 January, 2013. After he responds, it typically takes one week before you receive login details. Brian ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Anatoly Techtonik's contribution
On Wed, Dec 26, 2012 at 10:20 AM, Ezio Melotti wrote: > And a side effect of being welcoming is that you get every kind of people. > Different people have different behaviors and skills. I don't think his > lack of social skills is worse than e.g. the lack of English skills of some > of the contributors. In both cases the intentions are not bad, but the > message might be difficult to understand and thus can be misunderstood. > These people shouldn't be marginalized just because of their lack of skills. Now we're just trying to marginalize abuse. There is no lack of skills that is causing this, and it's not any sort of misunderstanding. Nick has presented numerous examples of this. ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Anatoly Techtonik's contribution
On Wed, Dec 26, 2012 at 8:09 AM, Ezio Melotti wrote: > That said, ISTM that the main problem is that the way he communicates is not > really effective and that results in an "energy drain" for other people. > This can be addressed on both the sides. > The community should ignore the tone of the messages or even the messages > themselves and most importantly avoid replies that convey the same negative > feelings. I've filtered his emails to the trash for almost two years now, but I'm not going to ignore that he's now discouraging my friends and colleagues from contribution. I already removed myself from the nosy list on a bunch of issues he created in the past, and the people who were willing to work with him are dropping off. I also will not ignore his tone about a GSoC contribution being useless. > People should be able to recognize when a discussion is not > constructive anymore and leave it, rather than wasting time just to prove a > point or to repeat themselves. (Note that this apply to everyone, and not > to anatoly in particular). > Regarding the effectiveness of the communications there's certainty room for > improvement, but apparently the previous attempts to address the problem > were unsuccessful. I'm willing to make an attempt myself, as I think I have > a quite clear idea of the problem. You're wasting your time if you think you will be the one to break through to him after several people have already talked to him. Apparently he even got on Skype with Guido about this. People would *pay* to have that chance. Anatoly got it for being a jerk and it changed nothing. ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Anatoly Techtonik's contribution
On Wed, Dec 26, 2012 at 7:28 AM, R. David Murray wrote: > Anatoly has been shaming us publicly for years. We would be much more > polite and rational in any more-public statement made (I trust). We > would still draw fire. That may or may not make us stronger in the > long run...for it to do so we will, in fact, need to have a principled > position to rest upon, and thus I think we would be well recommended > to have something PEP-like in terms of a policy statement. > > I wonder if a public discussion aimed at developing such a policy > would clue Anatoly in (probably not). I wonder what other communities > have done. I know Python is one of the leaders in the COC matter, > so perhaps we will have to be a leader here as well. > > This is not easy stuff. Any such CoC or policy should probably apply to all python.org mailing lists, and bolting one after things like -dev/ideas/list have been around for so long is going to be a hard task to get right. I do think something along the lines of a CoC is a good thing here, but I think it's much larger than python-dev and probably shouldn't be implemented as the result of or as a reaction to one person. I think it'd probably be a PSF-level thing to apply to python.org properties (a few discussions have kicked off, but nothing's more than an inch off the ground). I also think the process of creating a CoC that we don't immediately get burned at the stake for could take a long time to create and implement. I don't think we should have to put up with Anatoly while that process gets kicked around. ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Anatoly Techtonik's contribution
On Tue, Dec 25, 2012 at 4:56 PM, Łukasz Langa wrote: > Dnia 25 gru 2012 o godz. 13:37 Nick Coghlan napisał(a): > >> I'm well and truly to the point of caring far more about the feelings >> of people who get frustrated trying to deal with his obtuseness >> (whether that arises deliberately or through genuine cluelessness) >> than I care about his feelings. He has the entire internet to play on, >> we don't have to allow him access to python.org controlled resources. > > +1 > > I opened this thread so I feel somewhat responsible to carry this out to > finish. Give me a day or two to contemplate on how to achieve the following: > > 1. Communicate what happened clearly and openly to our community. > > 2. Communicate to Anatoly the decision to cut him off. > > 3. Arrange for feasible technological ways to execute the ban on python.org > resources, preparing also for vengeful action (which given the history is > unfortunately likely). > > 4. Prepare for rectifying unjust PR by the banned person, etc. > > I'm seriously considering writing all this as a PEP (most likely without any > personal details). I hope this won't be useful in the future but it might > help having this gathered as written policy, if only for transparency reasons. > > What do you think? > > I feel very bad that it has come to this but I strongly believe this is > necessary to protect us as a community. I think #2 is going to be hard to safely write if you intend to send it to python-dev addressed to Anatoly (which I got from #1). The shorter the better is my tip. I'm available to review/bikeshed about this email if you intend to write it. Also, please only post this to one list, preferably -dev and not -ideas. #3 can be handled pretty swiftly since the appropriate people are all involved in this conversation. On #4, whatever you do, please don't get involved in some back-and-forth post war and don't go around Reddit trying to further justify anything. If people talk, and they will, let them. Please don't write this up in a PEP. We're getting flak from all directions for code of conduct things on the PyCon/PSF side of things, and that's along the lines of what this would be. I actually do have some ideas in that area, but that's for another list and another time. This should just be an email. ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Anatoly Techtonik's contribution
On Wed, Nov 7, 2012 at 6:21 PM, John Benediktsson wrote: >> IMO he has a negative effect on the Python community. When he asks a >> question, he doesn't try to understand how Python is designed and let people >> think that the Python design just sucks (which is wrong, Python design is >> great! Python is the best language!). > > > Out of curiousity, I googled Anatoly and python-ideas and this thread[1] > seems a useful example. His suggestions seem intended to help, he provided > some code examples, and made only a handful of posts in support of his idea > (receiving a few negative responses). At times his English was rough, but > without going into the merits of his ideas - would an approach where you > encourage him to publish his ideas on PyPI or Github give him an outlet for > his energy? He's actually fairly active in Python-related open source as far as I've seen. I've come across his name as a contributor to several projects, so I don't think we need to offer him any outlets. > It seems to me his philosophy clashes with that of python-dev, perhaps his > batteries are a different size than those included in Python, but I'd like > to see this community be inclusive rather than exclusive, even at the > expense of a few added mail filters by the core team. It would be great to include him or leave him included, but I have the feeling that we're beyond this. I don't buy it that the problem is his English knowledge or that he doesn't know that there was a problem. Sure, he trips up on some English language skills, but those of us who have talked back to him have done so in what are pretty clear negative tones. He has reacted to said negativity with snark, so he gets it. His philosophy, back when I still read his emails, was that he is correct and to think otherwise is foolish (see his repeated attempts to get us to restructure the entire development process for him). We can ban him, we can keep him - whatever. My email filters will remain. ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Anatoly Techtonik's contribution
On Wed, Nov 7, 2012 at 10:38 AM, Chris Jerdonek wrote: > On Wed, Nov 7, 2012 at 6:08 AM, R. David Murray wrote: >> On Wed, 07 Nov 2012 14:26:15 +0100, wrote: >>> What can we do? Apart from the obligatory joke of nudging him gently >>> towards Ruby, I think calling his behavior out is a good idea. Cory >>> Doctorow also thinks that "many trolls are perfectly nice in real life >>> -- sometimes, just calling them on the phone and confronting them with >>> the human being at the other end of their attacks is enough to sober >>> them up" [3]. If that fails, banning him would show that we care about >>> the quality of communication and technical prowess is no excuse for >>> abusive behavior. >> >> As Brett pointed out, calling him on his behavior seems to meet with >> pretty much zero success as far as modifying his future behavior goes. > > Aside from calling him out on his behavior and trying to change it, > has anyone additionally made it clear to him that "if you continue > this behavior, you will be banned from [insert as appropriate]"? Or > is an explicit warning not needed? We could probably give him the explicit warning, and I suspect that may come out of the skype call that was mentioned, but I think he has to know by now that he's been toeing the line for probably 2 years. I used to try to work with him, then switched to trying to talk sense into him, then switched to defending why we do things, and then ended up filtering his emails. I've seen others lead down the same path. If he's actually reading what we're writing, it's never going in a positive direction with him. ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Commit rights for Hynek Schlawack
On Sun, May 13, 2012 at 1:50 PM, Antoine Pitrou wrote: > > Hello, > > Hynek Schlawack has now contributed several patches (11 of which appear > to have been committed) and has generally been pleasant to work with, > being both responsive to comments and able to produce quality patches. I > therefore propose to give him commit rights. What do you think? Sounds good to me. +1 ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Language summit
On Fri, Mar 9, 2012 at 02:04, Brian Curtin wrote: > > On Mar 8, 2012 10:32 PM, "Georg Brandl" wrote: >> >> Will we poor non-attendants get some minutes of what was discussed? >> >> Thanks, >> Georg > > I plan to take Senthil's, Eric Snow's, and my notes all together once > completed, then create a grand summary for all. I know Eric and I took pen & > paper notes so we'll need to transcribe, and I don't suspect I'll get to > that until I'm home - he thought the same. > > I'll try to have it ready as soon as possible. Only two days late, but I'll claim I was saving it as a happy Pi day present: http://blog.python.org/2012/03/2012-language-summit-report.html ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Language summit
On Mar 8, 2012 10:32 PM, "Georg Brandl" wrote: > > Will we poor non-attendants get some minutes of what was discussed? > > Thanks, > Georg I plan to take Senthil's, Eric Snow's, and my notes all together once completed, then create a grand summary for all. I know Eric and I took pen & paper notes so we'll need to transcribe, and I don't suspect I'll get to that until I'm home - he thought the same. I'll try to have it ready as soon as possible. ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Python Language Summit at PyCon US
On Tue, Jan 10, 2012 at 07:04, Michael Foord wrote: > Hello Python Committers, > > As usual we will hold a Python Language Summit before the PyCon US conference. > > If you have topics you would like to see on the agenda please also let me > know. I wouldn't mind a chat about what's happening with PEP-397 (Windows launcher), but I don't think there's a big enough Windows audience at the summit to put it on the agenda. If anyone there wants to talk about it before/after/at lunch/in a breakout session, I'd be interested. http://www.python.org/dev/peps/pep-0397/ ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Python Language Summit at PyCon
On Mon, Jan 30, 2012 at 13:28, Barry Warsaw wrote: > On Jan 30, 2012, at 07:17 PM, Michael Foord wrote: > >>I'd also be interested in what concrete things can be done in Python 3 to >>make web development easier. Unfortunately it would better if that discussion >>happened *after* the web-development summit, but if we have the right people >>at the language summit it may still be fruitful. > > Note that there is going to be a Python 3 panel at the web development > summit. I'm moderating it, but talk to Chris for details. > > I wish we could do more at Pycon to promote Python 3. Unfortunately we didn't get many proposals for 3.x talks this year. Myself and Senthil will be talking about it from a standard CPython view (mine is on Windows stuff, his is on general stdlib improvements), and there's a CherryPy 2/3 talk, but I believe that's about it. ~3/95 kind of sucks. ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Contributor Agreement
On Sun, Dec 4, 2011 at 16:01, Pat Campbell wrote: > Hi Frank: > > Thank-you for submitting your contributor agreement. It > > has been added to the online PSF bug tracker. > > > Also, I am forwarding your email to the "python-committers" > > mailing list in order for your inquiry to be addressed. > > > Python-Committers: > > > Please see Frank's question in the email below. > > > Thanks, > > Pat > > > > Pat > > > On Sat, Dec 3, 2011 at 10:24 PM, Frank Hellwig < > frank.hell...@lynxbridge.com> wrote: > >> Greetings, >> >> Attached is a signed contributor agreement as requested by the PSF. >> >> However, I do not see a clear link as how to contribute a module that I >> feel may be or use to the greater community or make it into the standard >> libraries as a utility module. Please advise. >> >> Thank you, >> >> Frank >> >> -- >> Frank Hellwig > >> LynxBridge, LLC http://www.lynxbridge.com/>> >> 12801 Worldgate Dr, Suite 500 >> Herndon, VA 20170 http://g.co/maps/ekn6>> >> 410-707-6136 (mobile) >> > > > > -- > Pat Campbell > PSF Administrator/Secretary > pat...@python.org > > ___ > python-committers mailing list > python-committers@python.org > http://mail.python.org/mailman/listinfo/python-committers > > Thanks, Pat. Frank - you might want to start a thread on the python-ideas [0] mailing list to propose your project for inclusion. From there a group will discuss it, perhaps suggest that it then goes to the python-dev list for a greater look from the full team, then perhaps create an issue on http://bugs.python.org to execute the work. [0] http://mail.python.org/mailman/listinfo/python-ideas ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Expiring MSDN Subscriptions
On Tue, Aug 9, 2011 at 16:22, Brian Curtin wrote: > We have a group of devs who received MSDN subscriptions around this time > last year which are now expired or about to expire. If yours is expired, > which you can find from > https://msdn.microsoft.com/en-us/subscriptions/manage/default.aspx, send > me your subscriber ID and the email address tied to your account and I'll > get it renewed for another year. The renewal takes roughly a week to > process, and I'd like to send the fewest emails to the fine folks at > Microsoft's Open Source Technology Center, so please respond soon so I can > send out a batch. > > If you don't currently have a subscription but would be interested in one, > let me know off-list and I'll gather some info from you and get you setup. > The main benefits are access to the full versions of Visual Studio and every > version of Windows. You also get access to what seems like anything > Microsoft has released, so you can relive Windows 3.1 if you want. > I just submitted a batch of renewals and first-time subscriptions for all who responded so far. If anyone else wants a renewal or first-time subscription, feel free to email me directly and I'll get it taken care of. Be on the lookout for mails from msdntnord...@arvatousa.com which is the order confirmation, and then one from msubs...@microsoft.com with activation details. ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
[python-committers] Expiring MSDN Subscriptions
We have a group of devs who received MSDN subscriptions around this time last year which are now expired or about to expire. If yours is expired, which you can find from https://msdn.microsoft.com/en-us/subscriptions/manage/default.aspx, send me your subscriber ID and the email address tied to your account and I'll get it renewed for another year. The renewal takes roughly a week to process, and I'd like to send the fewest emails to the fine folks at Microsoft's Open Source Technology Center, so please respond soon so I can send out a batch. If you don't currently have a subscription but would be interested in one, let me know off-list and I'll gather some info from you and get you setup. The main benefits are access to the full versions of Visual Studio and every version of Windows. You also get access to what seems like anything Microsoft has released, so you can relive Windows 3.1 if you want. ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Committer rights for Sandro Tosi
On Mon, Aug 1, 2011 at 09:00, R. David Murray wrote: > On Sun, 31 Jul 2011 19:53:00 +0300, Ezio Melotti > wrote: > > I would like to have Sandro added to the list of committers. > > He has been very active on the bug tracker, doing triaging work and > > contributing a number of patches. > > He also reported more than 40 issues, mainly about the documentation, > > and most of them have been fixed. > > Given Sandro's level of activity and the (at least for the ones I've > looked at, which granted haven't been many) accuracy of his doc patches, > I think he would be a valuable to have as a committer. From my > interactions with him I don't think we need to have any worry about > his going crazy with code commits...he's very aware of the need > to be conservative and get reviews. > > Ezio, are you volunteering to be his mentor? If so, then definitely +1. I haven't had much time to spend around python-dev lately, but my interactions with him on the tracker and IRC have been easy going and he has done good work, so I say +1 as well. ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] 3.2.1 rc 2
On Thu, May 19, 2011 at 13:33, Georg Brandl wrote: > As I've already said in another thread, I plan for 3.2.1 r2 as soon as > http://bugs.python.org/issue12084 is fixed. This is hopefully this > weekend, but may be next. Final is, as always, one week later. > > Georg Sorry for taking so long to finish it, but I now have a patch completed for #12084. It's Windows specific so I don't imagine there are a lot of interested reviewers, but at least a quick look to make sure I'm not doing anything too crazy would be greatly appreciated so Georg and the crew and get on with the release process. The full test suite passes, but keep in mind that symlinks on Windows require administrator privileges. My build slave is the only one which runs as admin and it's not currently running very well. Now that I fixed this bug, I'll get the bot back up and running. ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Charles-François Natali (neologix)
On Sun, May 15, 2011 at 03:31, Victor Stinner wrote: > Hi, > > This guy rocks! He understood and fixed many subtle bugs like race > conditions recently. Example from the NEWS of Python 3.3: > > - Issue #12060: Use sig_atomic_t type and volatile keyword in the signal > module. Patch written by Charles-François Natali. > > - Issue #11849: Make it more likely for the system allocator to release > free()d memory arenas on glibc-based systems. Patch by > Charles-François > Natali. > > - Issue #10517: After fork(), reinitialize the TLS used by the > PyGILState_* > APIs, to avoid a crash with the pthread implementation in RHEL 5. > Patch > by Charles-François Natali. > > - Issue #11650: PyOS_StdioReadline() retries fgets() if it was > interrupted > (EINTR), for example if the program is stopped with CTRL+z on Mac OS > X. Patch > written by Charles-Francois Natali. > > - Issue #11811: ssl.get_server_certificate() is now IPv6-compatible. > Patch > by Charles-François Natali. > > - Issue #8428: Fix a race condition in multiprocessing.Pool when > terminating > worker processes: new processes would be spawned while the pool is > being > shut down. Patch by Charles-François Natali. > > - Issue #11757: select.select() now raises ValueError when a negative > timeout > is passed (previously, a select.error with EINVAL would be raised). > Patch > by Charles-François Natali. > > etc. > > I would to propose him to commit grant. What do you think? > > Victor +1, he's been involved in some tougher issues and has been active for a while now. I haven't looked at many of his patches but he has written several, and his comments on issues have been pretty thorough. ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
[python-committers] Quick survey for PyCon talk on core development
Hi all, If you have a few free minutes, would you mind filling out a couple of questions? I'm giving a talk at PyCon about core development [0] and wanted to sprinkle in some info about the people doing the work. https://spreadsheets.google.com/viewform?formkey=dEZXWVhQMnBGREU0TUl0TTRTWk1zOEE6MQ Feel free to answer or skip any questions. Your name isn't associated with it. Thanks a lot for your time, and I look forward to seeing any of you at PyCon! Brian [0] http://us.pycon.org/2011/schedule/presentations/7/ ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Commit privileges for Łukasz Langa
On Sun, Sep 5, 2010 at 09:43, Antoine Pitrou wrote: > > Hello, > > I propose we give commit privileges to Łukasz Langa. He has submitted > various non-trivial patches of rather good quality (for example new > features for ConfigParser), some of which have already been committed; > it seems that he's motivated to further contribute. > > Perhaps other devs want to share their opinion on this. > > (for the curious, his tracker id is lukasz.langa) > > Regards > > Antoine. +1 from me. The patches I've reviewed from him have been well made and thought out. He is also pretty open and receptive to review comments and discussion about his work. ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] New comitter proposal: Terry Reedy
On Mon, Jul 19, 2010 at 17:46, Kurt B. Kaiser wrote: > > He's made the comment a couple of times recently that he doesn't have a > development environment and can't make patches. That's unusual. > However, since IDLE is pure Python, the necessary development > environment is minimal, I'd be happy to help him get set up. I'm pretty > sure he has pretty much everything he needs already. Terry, You might be interested in this doc I just wrote up for the PSF sprint group: http://docs.pythonsprints.com/core_development/beginners.html. It could use a more accurate/friendly compilation setup for Mac/Linux (I've done it in the past, I just have no idea what I did), but a few interested beginners have looked it over and said it was helpful. Although a Windows development environment can be had with free (as in beer) tools, I can ping our contact at Microsoft for MSDN subscriptions as needed. Brian ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] New comitter proposal: Terry Reedy
On Sat, Jul 17, 2010 at 20:09, Nick Coghlan wrote: > I'd like to propose Terry Reedy as a new comitter. > > He has been contributing to Python via the tracker, c.l.p, python-dev > and python-ideas for years and has recently requested commit > privileges in order to work on IDLE. I think we should give them to > him :) > > Terry's been around long enough that I don't think he'll need much (if > any) mentoring, but I'm certainly willing to provide any that is > needed. > > Cheers, > Nick. +1 He has been active for quite a while, contributes quality work on the tracker, and of course the recent IDLE stuff. ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] New committer proposal: Alexander Belopolsky
On Thu, May 20, 2010 at 15:28, Mark Dickinson wrote: > I propose that Alexander Belopolsky be given svn commit access. > +1. Although I'm a relative newcomer I've seen his name on a lot of issues, most often associated with a quality patch or thorough review. ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Proposing Tim Golden as a Committer
On Mon, Apr 19, 2010 at 15:30, "Martin v. Löwis" wrote: > > I would like to propose Tim Golden as a Python committer. > > Anybody supporting this addition? > > > At the very least we should grant Tim tracker privileges as he > > frequently responds to issues. > > Done! > > Martin +1. Tim seems to be a pretty sharp Windows guy (especially witnessed in his WMI project), and his contributions look good. ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
