On Fri, Nov 3, 2017 at 11:30 PM, Nick Coghlan wrote:
> On 4 November 2017 at 09:52, Jelle Zijlstra wrote:
>>
>> 2017-11-03 16:44 GMT-07:00 Joao S. O. Bueno :
>>>
>>> This just popped up in Brython's issue tracker discussion:
>>>
>>> """
>>> Pierre Quentel
>>>
>>> 04:57 (16 hours ago)
>>> to bryt
+1 from me. I first had an idea to give Ivan commit privileges when I
was merging his PEP 526 implementation, so I think it's long overdue.
Yury
On Tue, Dec 5, 2017 at 8:00 PM, Guido van Rossum wrote:
> I'd like to propose Ivan Levkivskyi as a new core committer. He's
> (re-)written most of the
Hi,
I want to propose granting commit privileges to Nathaniel J. Smith.
He's interested in the idea of becoming a core developer, and given
the quality of his contributionsI think he won't need any extensive
mentoring (although I'll be happy to assist Nathaniel in the
beginning).
Nathaniel has be
Developers team?
Yury
On Thu, Jan 25, 2018 at 10:33 AM, Ezio Melotti wrote:
> +1
>
> On Thu, Jan 25, 2018 at 12:23 AM, Yury Selivanov
> wrote:
>> Hi,
>>
>> I want to propose granting commit privileges to Nathaniel J. Smith.
>> He's interested in the
+1.
Yury
On Fri, Apr 13, 2018 at 8:13 AM, Nick Coghlan wrote:
> Hi folks,
>
> I'd like to propose Petr Viktorin as a specialist core developer,
> focusing on extension module imports.
>
> Petr was the primary designer & implementer for the accepted PEP 489
> multi-phase extension module initiali
On Thu, Apr 26, 2018 at 10:12 AM Victor Stinner wrote:
[..]
> I identified 3 obvious subteams:
> * Documentation
> * IDLE
> * asyncio
Sorry, asyncio isn't an obvious choice for me. There are not so many
low-hanging fruits left in asyncio except improvements to its
documentation. I'm a firm -1 to
-1
On Wed, May 2, 2018 at 10:02 AM Eric Snow
wrote:
> On Wed, May 2, 2018 at 3:49 AM, Victor Stinner
wrote:
> > The poll is on the *current* PEP. I propose 4 choices:
> >
> > * +1: you like the PEP
> > * -1: you dislike the PEP
> > * 0: you are not sure if you like it or not, or you have no opin
+1
Yury
--
Yury
___
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/
Thank you, Guido. This is a sad day for me personally; I really hoped
you'd lead Python for a few more years. On the other hand, Python is
in good hands, you've built a large enough and diverse community
around it!
As for the new governing model, I imagine that we don't need to make
any decision
On Thu, Jul 12, 2018 at 12:58 PM Antoine Pitrou wrote:
>
>
> I'd like to point out that the N-virate idea doesn't handle a key issue:
> once you have a N-virate, how do you evolve its composition according to
> the implication and motivation of its members - but also to remarks or
> frustation by
On Thu, Jul 12, 2018 at 1:50 PM Brett Cannon wrote:
[..]
>> One way would be to re-elect them every 5 or so years. Essentially,
>> an N-virate is a dictator-like entity for a few years.
>
>
> But that doesn't help deal with inconsistency since that just means we have
> consistency for 2 releases
On Sat, Jul 14, 2018 at 10:07 PM Brett Cannon wrote:
[..]
>> Ideally Guido would accept the PEP but I'm not sure if he is willing to. If
>> that is indeed the case then how should this be done so that the document is
>> universally accepted by all committers?
>
>
> In my ideal scenario, people w
On Thu, Jul 19, 2018 at 5:36 AM Nathaniel Smith wrote:
> What would be a good date? The core sprint is coming up Sept. 10-14,
> and this seems to be a likely topic of conversation there. And then
> after the sprint, those who aren't present will need time to catch up
> with any discussions that h
On Wed, Aug 1, 2018 at 5:26 PM Nathaniel Smith wrote:
[..]
> Now we have to figure that out: the legitimacy of any new governance
> system is ultimately going to have to rest on the consensus of the
> core devs. The only way I know to get that is by taking the time to
> work through the difficult
On Wed, Aug 1, 2018 at 6:44 PM Mariatta Wijaya
wrote:
>
>
> Thank you for the responses and concerns.
>
> I do want to keep this discussion open and ongoing, and I still think that we
> do need a set deadline on things.
I talked to a few core developers recently (at EuroPython and over
messenger
On Wed, Aug 1, 2018 at 8:29 PM Mariatta Wijaya
wrote:
[..]
> Please don't misunderstand my wanting to set up a deadlines and process as
> wanting to rush things.
Absolutely, I understand, I didn't want to imply that "[name] is
rushing the process". Sorry if I sounded this way. I do have an
impre
On Thu, Aug 2, 2018 at 4:43 PM Brett Cannon wrote:
>
> On Wed, 1 Aug 2018 at 17:58 Yury Selivanov wrote:
>>
>> On Wed, Aug 1, 2018 at 8:29 PM Mariatta Wijaya
>> wrote:
>> [..]
>> > I'm open to extend the dates, and even wait another year if we need
On Thu, Aug 2, 2018 at 3:55 PM Jack Jansen wrote:
>
> Nathaniel, you strike the nail on the head here.
>
> The reason Guido as BDFL and therefore ultimate authority on what “python” is
> worked because it is organic: it is not set down in strict rules and
> regulations and timelines and percenta
Hi Antoine,
I'll try to find some time and help. I'm not sure how much time I can
contribute exactly, but I at least can help with a review and maybe
brainstorm. Count me in.
Yury
On Wed, Aug 8, 2018 at 1:39 PM Antoine Pitrou wrote:
>
>
> Hi all,
>
> I contacted Nathaniel and the people who had
On Thu, Sep 20, 2018 at 4:37 PM Antoine Pitrou wrote:
>
>
> Apparently it's this one:
> https://mail.python.org/pipermail/python-ideas/2018-September/053482.html
After reading the original email I, personally, am in support of the
WG & Brett's decision.
I also think that we need a neutral third-
What's the current plan for what version of Python we release after 3.9?
The reason I'm asking this is because I frequently need to refer to
*that version* of Python in the documentation, especially when I'm
deprecating APIs or behavior. Right now I'm saying "Python 4.0"
implying that 4.0 will be
On Tue, Sep 25, 2018 at 4:38 PM Serhiy Storchaka wrote:
[..]
> 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 c
On Tue, Sep 25, 2018 at 5:18 PM Nathaniel Smith wrote:
>
> On Tue, Sep 25, 2018, 12:30 Yury Selivanov wrote:
>>
>> The reason I'm asking this is because I frequently need to refer to
>> *that version* of Python in the documentation, especially when I'm
>>
On Tue, Sep 25, 2018 at 6:33 PM Victor Stinner wrote:
>
> Hi,
>
> I would prefer to never ever break the backward compatibility in Python. To
> make it clear I suggest to use 4.0 for the release following Python 3.7.
I think Serhiy made a strong argument that the code like below would
break if w
On Wed, Sep 26, 2018 at 12:28 PM Brett Cannon wrote:
[..]
>> What is the status of Brett's UNIX Python launcher "py" by the way?
>
>
> You can see the current TODO list at https://crates.io/crates/python-launcher
> . Basically I need to implement "--help" and "--list" to fill in the last two
> l
On Wed, Sep 26, 2018 at 1:25 PM Paul Moore wrote:
[..]
> but I don't know how
> useful it would be in practice - can you give some examples of use
> cases?)
It's hard to give a real life example as "py" doesn't support this,
but I can imagine the following scenario: if I have a script that uses
s
On Thu, Sep 27, 2018 at 2:19 PM Brett Cannon wrote:
>
> Since there isn't a way to do this in any fashion I never really thought
> about it. I think most people either set the shebang to the version of Python
> they want it to work with, have pip install the entry point which will also
> set th
On Sat, Sep 29, 2018 at 10:16 AM Steven D'Aprano wrote:
[..]
> Well, I could announce it, but nobody would pay any attention. Why
> should we pay attention to this announcement? No offense to Łukasz, but
> how did he get put in charge of this?
You could and everybody would pay attention.
As for
I created a poll to promote Kyle Stanley as a core dev.
Please read more and vote here:
https://discuss.python.org/t/vote-to-promote-kyle-stanley/3839.
Thank you!
Yury
___
python-committers mailing list -- python-committers@python.org
To unsubscribe se
On Mon, Jul 6, 2020 at 7:21 PM Raymond Hettinger
wrote:
> If not, perhaps we should just have a single beta, frozen except for bugfixes.
+1 for having betas frozen, except for bug fixes. But the bug fixes
need to go somewhere, so I propose to have yet another frozen beta (if
there are bug fixes,
On Thu, Jul 23, 2020 at 8:53 AM Nathaniel Smith wrote:
>
> On Thu, Jul 23, 2020, 05:25 Jack Diederich wrote:
>>
>> I'm sorry we had to ban Guido for three months but maybe he'll learn his
>> lesson and not merge commit messages that include screeds about "relics of
>> white supremacy".
>
>
> I'
Hello,
Thank you very much for accepting me as a member of your team!
Python is the most beautiful, simple and complex language I
ever knew, and it's an honor for me to help to make it better.
Just to give you an idea of how passionate I am about python,
I'd like to tell you a short story. When
Hello,
I'm having difficulty with replying to a message in rietveld.
Here's a screenshot of the exception: http://goo.gl/70iQ5v
(AttributeError at /review/20356/publish)
Is this a known issue? Maybe I'm doing something wrong?
Yury
___
python-committe
I've tried multiple times, yes.
Yury
On 1/27/2014, 2:56 PM, Antoine Pitrou wrote:
On lun., 2014-01-27 at 14:52 -0500, Yury Selivanov wrote:
Hello,
I'm having difficulty with replying to a message in rietveld.
Here's a screenshot of the exception: http://goo.gl/70iQ5v
(At
it 'reply' link for it
5. Erase everything from the text area and type something in
5. Submit the form.
Yury
On 1/27/2014, 3:13 PM, R. David Murray wrote:
On Mon, 27 Jan 2014 14:52:16 -0500, Yury Selivanov
wrote:
Hello,
I'm having difficulty with replying to a message in rietvel
On more note:
I'm using open-id (google) to sign in on bugs.python.org
Yury
On 1/27/2014, 3:24 PM, Antoine Pitrou wrote:
On lun., 2014-01-27 at 15:18 -0500, Yury Selivanov wrote:
OK, I've tried another browser (regularly I use Safari, this
time I was trying it with Chrome) --
Martin,
On 1/27/2014, 5:01 PM, "Martin v. Löwis" wrote:
Am 27.01.14 21:18, schrieb Yury Selivanov:
OK, I've tried another browser (regularly I use Safari, this
time I was trying it with Chrome) -- same thing.
For those who want to try to reproduce it:
1. Open http://
On 1/28/2014, 2:07 AM, "Martin v. Löwis" wrote:
Am 27.01.14 23:37, schrieb Yury Selivanov:
So, the JS code is clearly working.
Unfortunately, I have no idea what the root problem might be.
a) I cannot reproduce it. Following your steps, I manage to post a
reply every time.
b)
Hello,
Another quick infrastructure question (is this the right list, btw?):
I don't see 'review' links for some patches. Like in issue #14911,
Kristján uploaded two patches, same day, almost same time, and I
see a review link only for one of them.
Screenshot: http://goo.gl/HK2oer
Thanks,
Yury
OK, thank you.
Are you sure it's the right thing to do? I.e. a user can create a
patch, ensure that it applies cleanly, and while he uploads it,
someone pushes to the repo. No 'review' link, no notification.
Wouldn't it make sense to always show the review link, and let
the user to resolve the c
Hi,
Do we have a mail list/group where we can discuss the
python.org site?
I've noticed some typos and have some advices, like:
- Python logo has a little yellow 'BETA' label, which may give
some new users impression, that it is the Python Language Beta,
not the python.org website.
- Upcoming
On 2/19/2014, 11:31 PM, Yury Selivanov wrote:
Hi,
Do we have a mail list/group where we can discuss the
python.org site?
I've noticed some typos and have some advices, like:
- Python logo has a little yellow 'BETA' label, which may give
some new users impression, that i
Hi Brian,
My subscription expires today.. Is it possible to renew it somehow?
Thanks,
Yury
On 2014-11-14, 4:39 PM, Vinay Sajip wrote:
Brian Curtin python.org> writes:
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 MS
Larry,
On 2015-05-12 1:04 PM, Larry Hastings wrote:
Workflow 1
==
When I ship beta 1, we create the 3.5 branch. trunk become 3.6.
When I ship rc 1, the 3.5 branch becomes 3.5.1. I maintain a
publically visible repo /on bitbucket/ for 3.5.0, and we use bitbucket
"pull requests" for
Hi,
I can't post messages to the code review tool -- it shows
me 500 error page.
I'm not sure if I'm the only one who is experiencing this.
I tried different browsers, cleaning cookies/local storage
etc.
I can change my password and give my login credentials for
someone to debug/test.
Yury
__
Hi,
docs.python.org is kind of broken for 3.5. For instance, "what's new in
3.5" link points now to a missing whatsnew for 3.6 (which gives us 404
error). Version switcher extension should also be updated in 2.7, 3.4,
3.5, and 3.6 branches. I think I could fix that all myself, but I don't
Benjamin's commits to fix version switcher helped a little bit, but docs
for 3.5 are still broken (and 3.6 FWIW).
Yury
On 2015-05-27 6:23 PM, Yury Selivanov wrote:
Hi,
docs.python.org is kind of broken for 3.5. For instance, "what's new
in 3.5" link points now to a miss
Hi Nick,
I've added myself to dis & contextlib modules on the experts list.
Yury
On 2015-06-27 12:47 AM, Nick Coghlan wrote:
Hi folks,
My available time for the fundamentals of stdlib module maintenance is
unfortunately pretty limited these days, which means even reviewed
patches for modules
Hi,
Does anybody know what happened to daily-refleaks?
Yury
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
On 2015-09-10 3:23 AM, Antoine Pitrou wrote:
Apparently the hg clone had gone in a mess:
pulling from https://hg.python.org/cpython
searching for changes
abort: abandoned transaction found - run hg recover!
I cleaned it up, it should work again next night.
Thank you, Antoine!
Yury
__
Most of the emails from bugs.python.org (and review tool) end up being
marked as spam in gmail. I consistently miss 70% of them. Is it
possible to fix this?
Yury
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/
On 2015-11-18 5:49 PM, Ezio Melotti wrote:
On Thu, Nov 19, 2015 at 12:40 AM, Yury Selivanov
wrote:
>Most of the emails from bugs.python.org (and review tool) end up being
>marked as spam in gmail. I consistently miss 70% of them. Is it possible to
>fix this?
>
A quick work
Hi,
I want to propose to give commit privileges to INADA Naoki. He's the
guy behind compact dict implementation for CPython 3.6, which was a
super complex patch. He also participated in many asyncio related
discussions/PRs, on python-ideas and bug tracker.
He's quite interested in becoming
sum wrote:
> I'm with Nick. Assuming Yuri wants to mentor Inada I'm all for giving
> him commit privileges!
>
> On Sun, Sep 25, 2016 at 9:00 PM, Nick Coghlan wrote:
>> On 26 September 2016 at 03:52, Raymond Hettinger
>> wrote:
>>>
>>>> On Sep 25
Thanks, Victor!
On Mon, Sep 26, 2016 at 5:27 PM, Victor Stinner
wrote:
> https://docs.python.org/devguide/coredev.html gives some steps ;-)
>
> 2016-09-26 17:23 GMT+02:00 Yury Selivanov :
>> Thank you guys. I'll send a detailed email to INADA, explaining most
>> b
Does anyone know where's "daily reference leaks"? Last email was sent
on Sun Jul 10 05:57:30 EDT 2016. Just today I found two memory leaks in
3.6, it might be many more that we don't know about.
Yury
___
python-committers mailing list
python-commi
On 2016-11-08 7:36 PM, Antoine Pitrou wrote:
Le 09/11/2016 à 01:24, Yury Selivanov a écrit :
Does anyone know where's "daily reference leaks"? Last email was sent
on Sun Jul 10 05:57:30 EDT 2016. Just today I found two memory leaks in
3.6, it might be many more that we don&#x
On 2017-01-20 8:38 AM, Stefan Krah wrote:
I'm still very interested of course to have an official FASTCALL API
for third party modules that don't (and probably should not) use AC.
AFAIK, even though FASTCALL isn't "official", Cython already
uses it.
Yury
_
Thanks for this email Victor, it illustrates a lot of pain-points
that some core devs have with CPython development process.
I think that we are lucky that we have you and Serhiy who spend
so much time to push so many improvements to the CPython internals.
I think that while we are working on a n
On 2017-01-20 5:02 PM, Lukasz Langa wrote:
On Jan 20, 2017, at 9:26 AM, Yury Selivanov wrote:
I think that we need to become less conservative about
development of CPython internals. At this point it's impossible
to make CPython any faster without invasive refactorings, and
I think it
Hi,
First, I'm really happy that we moved to git and GH. The GH review tool
is super convenient and CI integration helps.
I'm less happy about requiring to make a PR for every commit. It's a no
problem for new features development, but it's a huge pain for a bug
fixing workflow. Last week
Hi Brett,
On 2017-03-14 6:00 PM, Brett Cannon wrote:
[..]
Yesterday I was working on a few asyncio PRs and a bug in async/await.
All PRs required cherry-picking. Again, I was spending significant
amount of time just creating branches/PRs for cherry-picking.
Were you creating the
On 2017-03-16 12:16 PM, Brett Cannon wrote:
On Wed, 15 Mar 2017 at 20:24 R. David Murray <mailto:rdmur...@bitdance.com>> wrote:
On Wed, 15 Mar 2017 22:56:33 -0400, Yury Selivanov
mailto:yselivanov...@gmail.com>> wrote:
> It's not just long waiting time
63 matches
Mail list logo
