[python-committers] Nikita Sobolev is now a member of the Python Triage Team
Hi I am very happy to share that Nikita Sobolev is now a member of the Python Triage team. https://github.com/python/core-workflow/issues/422 Nikita contributes various parts of CPython and he is a passionate contributor to Python, not only on CPython project but also on the mypy project and the typeshed project. - https://github.com/python/cpython/commits?author=sobolevn - https://github.com/python/mypy/commits?author=sobolevn - https://github.com/python/typeshed/commits?author=sobolevn And he sends me a mail about what he interested in CPython Here is the list - Typing - Unittest, doctest, and tests. - Enum - AST-Tooling After I mentor the triage role itself for 4 weeks, I wish that any of the core dev who need more resources for those parts would mentor him for his next step. One more thing, he is an amazing rock start in the Github universe :) https://stars.github.com/profiles/sobolevn/ Happy New Year and Welcome on board Nikita! Warm regards from Korea, Dong-hee -- Software Development Engineer at Line corp. Tel: +82 10-3353-9127 Email: donghee.n...@gmail.com | donghee...@python.org | donghee...@linecorp.com Linkedin: https://www.linkedin.com/in/dong-hee-na-2b713b49/ ___ 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/LEYCLS3QLEBSYFPG5MN3L2M4F26P5QIE/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: What's the schedule for the core sprint?
Hi, Eric I sent you a direct mail about the Discord server :) Regards, Dong-hee 2021년 10월 18일 (월) 오전 10:48, Eric V. Smith 님이 작성: > I'm traveling and I don't know when I'll be free. If there's a schedule > of any events, I'll try and make some of those. > > Also, any instructions for Discord (URL, how to get to the core sprint > channel(s)) would be appreciated. I don't know much about Discord. > > Thanks. > > > > ___ > 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/LLXNUWXCPYQLYJTYYENYR3U47CS3DB64/ > Code of Conduct: https://www.python.org/psf/codeofconduct/ > ___ 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/FOW6DDN2QLXA563NAVNMAQOSEHBDA3X5/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: Opting-in for Hacktoberfest
> +1 to this initiative. +1 also 2021년 10월 6일 (수) 오전 2:13, Senthil Kumaran 님이 작성: > On Tue, Oct 05, 2021 at 09:46:44AM -0700, Mariatta wrote: > > > > I do have the ability to add/remove hacktoberfest topic myself, so if > we're > > okay with this, I can go ahead and do it. I will also remove the topic > once the > > month ended. > > +1 to this initiative. > > -- > Senthil > ___ > 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/YDIETD6QAKQCJW5ZFXMVRRGLNIGEVA7Z/ > Code of Conduct: https://www.python.org/psf/codeofconduct/ > ___ 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/S6GB32OZKSGT6LFNXFHUDGFZZ4LAD7LI/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: Welcome Ken Jin to the team!
Welcome Ken Jin :) 2021년 8월 27일 (금) 오전 3:44, Brett Cannon 님이 작성: > > ___ > 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/VUIND4NXY74E7Y75AKLR5FVPQVSM6MJL/ > Code of Conduct: https://www.python.org/psf/codeofconduct/ > ___ 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/PHGGP36PE7CAXXOHQD4C3ZFUMB44Z6HZ/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: Dennis Sweeney is now a member of the Python Triage team
Congrats Dennis! I can not believe that you were not a triage member :) Personally, I am a big fan of your fast search patch! I am looking forward to your future contributions! Regards, Dong-hee 2021년 7월 28일 (수) 오전 1:25, Zachary Ware 님이 작성: > Hi all, > > Just a quick note to mention that Dennis Sweeney (CC'd) has been added > to the Python Triage team: > https://github.com/python/core-workflow/issues/412. Dennis has > already been responding to new issues, and the newly added permissions > will enable better responses and corrections to issue/PR metadata. > > Welcome, Dennis! > ___ > 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/YSLNWZHDJK63HH4X4NI4LG2SN3DCCDPK/ > Code of Conduct: https://www.python.org/psf/codeofconduct/ > ___ 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/PBFM63LU7F27QV75CLVDV4MWVVWP3D34/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: Developer in Residence Weekly Report, July 12 - 18
Thanks for all your effort! Regards, Dong-hee 2021년 7월 17일 (토) 오후 8:29, Łukasz Langa 님이 작성: > Hello there, > finishing up on the inaugural week, number-wise we're looking as > follows: I closed 14 issues and 54 PRs, reviewed 9 PRs, and authored 6 own > PRs. > > Details at: https://lukasz.langa.pl/1c78554f-f81d-43d0-9c89-a602cafc4c5a/ > > - Ł > ___ > 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/BH3BXUROL23O5W3SNILHV6SP5E2OH3KN/ > Code of Conduct: https://www.python.org/psf/codeofconduct/ > ___ 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/A7JVNSUJYX7OS7E3P53CVHCJI5L2GZAH/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: PSF hires first Developer-in-Residence (was: Re: Re: Call for resumes: Developer-in-Residence to support CPython)
Congrats! Warm Regards Dong-hee 2021년 7월 13일 (화) 오전 12:45, Ewa Jodlowska 님이 작성: > Hi folks - > > Just to circle back, we have officially contracted with Łukasz Langa to be > the first CPython Developer-in-Residence! > > PSF announcement: > https://pyfound.blogspot.com/2021/07/ukasz-langa-is-inaugural-cpython.html > > We look forward to seeing all the impact that Łukasz and this role will > have! > > Best wishes, > > Ewa > > On Thu, May 13, 2021 at 3:41 PM Ewa Jodlowska wrote: > >> Hi folks - >> >> Just a reminder that we are still accepting resumes for the >> Developer-in-Residence role. >> >> The deadline to submit a resume is May 16th. >> >> If you would like to chat tomorrow, Saturday or Sunday, let me know. I am >> happy to share how the employee will work with the PSF and expectations. >> >> >> Ewa Jodlowska >> Executive Director >> Python Software Foundation >> e...@python.org >> >> >> On Mon, Apr 5, 2021 at 4:00 PM Brett Cannon wrote: >> >>> >>> >>> On Mon, Apr 5, 2021 at 12:57 PM Ewa Jodlowska wrote: >>> On Mon, Apr 5, 2021 at 2:36 PM Victor Stinner wrote: > Hi Ewa, > > This is really awesome! It's great that the PSF can now hire someone > for that! > > The job offer is great, but I would like some clarification :-) (While > I was part of the previous Steering Council who helped to write the > job offer, sadly I was not avaialble last months when it was > discussed.) > > > Who is going to "manage" the candidate? > Great question! The technical direction will come from the SC and the people management will be Ee and myself. > > > On Mon, Apr 5, 2021 at 7:30 PM Ewa Jodlowska wrote: > > The Developer-in-Residence will work full-time for one year to > assist CPython maintainers and the Steering Council. Areas of > responsibility will include analytical research to understand the > project's > volunteer hours and funding, investigation of project priorities and their > tasks going forward, and begin working on those priorities. We are looking > to hire an existing core developer because of the type of work involved > and > interaction with volunteer core developers and contributors. Need and > available funding will determine any extension beyond the first year. > > > > Create metrics (...) Combine usage and surveyed metrics to determine > which standard library modules need help and what the maintainer cost is > for standard library modules > > What are the expected steps after the production of such report of the > stdlib usage and maintenance? Hire more people to maintain most used > stdlib modules, or deprecate least used modules? > > For example, asyncio and ctypes are popular but barely maintained. For > the CI, the most unstable test is test_asyncio (I asked for help > multiple times on python-dev). Do we need a more detailed reports on > the 302 (len(sys.stdlib_module_names)) stdlib modules? > One of the intentions is to document these cases to better prioritize funding we have and provide direction to potential future funders. I am sure someone from the Steering Council will want to chime in on additional, more technical intentions :) >>> >>> I think the results of the research is going to help inform what the >>> next steps are (hence the need for the research 😉). Guessing what needs >>> work and making a call without having at least *some* form of data >>> seems premature. I also have stdlib data already for a language summit >>> discussion (if it gets selected), and at worst I will just open source the >>> Jupyter notebook with the charts of what I found so this won't be starting >>> from scratch. >>> >>> Plus I suspect there will be some discussion here of what people want to >>> see be worked on. While the SC is the final decider on the priorities >>> simply because it would probably be a bit chaotic if the whole team tried >>> to direct a single person's work, that doesn't mean things won't be >>> discussed here to provide guidance and feedback to the SC. >>> >>> > > I understand that the first step is to put priorities in bug triage > and PR reviews for the candidate. > > > > Address Pull Request and Issue backlogs based on the developed > metrics and other metrics created by the Steering Council > > What about the candidate skills? I don't expect the candidate to be > able to fix any bug in any part of the Python. What if is the priority > is a module that the candidate doesn't know? They should do their > best, help debugging issues and propose a fix? I expect the existing > module maintainers to remain the local autority to review pull > requests written by the candidate, to avoid mistakes. > >>> What would *you* do in this situation? The expectation is th
[python-committers] Re: core-dev chat
> If you're not familiar with > Zulip, it will take little time before you can use it reasonably well. > Same for Slack, Discord, Gitter... and also Discourse, by the way. > Mostly because people go where their friends / colleagues / > acquaintances are. In other words, those are network effects and have > nothing to do with the UI friendless of each system. For example, I have > to use Slack at work, yet I find Zulip far more convenient. I think that we are on the same side about the considerations points but my observation bias is weighted on Slack, Discord, Teams. So I agree with you and my suggestion may not be an objective perspective. But I think that if we decide to choose to adopt new communication tools, I think that we can remove the danger factor which makes people not use after some period. And I think that it will show a higher survival probability when people feel comfortable than people feel not convenient. (Please note that convenience or comfort does not mean the systems perfectness) > In other words, those are network effects and have > nothing to do with the UI friendless of each system. The reason why I mentioned the 'UI friendless' is that we are discussing the communication tools for programming projects. IMHO, the network effect of business communication tools world is that how many people use the tool for their work. if we can not choose the most people convenient tool of the programming world, but we can choose the second one as the alternative one. For example, as you said you use Slack for your work purpose if we choose Slack (if we decide to adopt new tools) at least you and I don't have to learn how to use Zulip fluently. And I think that it can also apply to other core devs and contributors who feel comfortable with Slack or Slack-like UI/UX. Regards, Dong-hee 2021년 5월 15일 (토) 오후 11:45, Antoine Pitrou 님이 작성: > > Le 15/05/2021 à 16:37, Dong-hee Na a écrit : > > > You still haven't explained why e.g. Zulip > > > > I think that Zulip is a good service and AFAIK Zulip is the OSS project > > based on Python. > > But I think that such communication tools should be evaluated not only > > technology side but also on how people feel familiar with UI/UX. > > I don't want to evaluate the UI/UX accessibility of Zulip is good or bad > > but it's the issue of how people feel familiar. > > I don't think that's an important concern. We're talking about chat > systems, which are all really approchable. If you're not familiar with > Zulip, it will take little time before you can use it reasonably well. > Same for Slack, Discord, Gitter... and also Discourse, by the way. > > On the scale of UI friendliness, all those systems are on the "easy" > side (compare with the git CLI, which is on the "difficult" side). > > > This phenomenon also occurs in other common (non-business) messengers. > > (WhatsApp, Facebook Messenger, etc..) > > You can observe that there is no single monopoly messenger which concurs > > worldwide. > > Mostly because people go where their friends / colleagues / > acquaintances are. In other words, those are network effects and have > nothing to do with the UI friendless of each system. For example, I have > to use Slack at work, yet I find Zulip far more convenient. > > Regards > > Antoine. > ___ > 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/ZKS7V5QJ4LM4TFMBXGAJR4ZXMK27BJUR/ > Code of Conduct: https://www.python.org/psf/codeofconduct/ > ___ 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/OWC6WQ2ZRE5D2E2P44VAVD4XJTQHJSAW/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: core-dev chat
> You still haven't explained why e.g. Zulip I think that Zulip is a good service and AFAIK Zulip is the OSS project based on Python. But I think that such communication tools should be evaluated not only technology side but also on how people feel familiar with UI/UX. I don't want to evaluate the UI/UX accessibility of Zulip is good or bad but it's the issue of how people feel familiar. This phenomenon also occurs in other common (non-business) messengers. (WhatsApp, Facebook Messenger, etc..) You can observe that there is no single monopoly messenger which concurs worldwide. The list of tools that I suggested is based on my personal observation which is normally used in tech companies. If people feel familiar and such things can address people's productivity I think that that's a good reason to choose. Regards, Dong-hee 2021년 5월 15일 (토) 오후 11:16, Antoine Pitrou 님이 작성: > > Le 15/05/2021 à 13:23, Senthil Kumaran a écrit : > > On Sat, May 15, 2021 at 11:13:48AM +0900, Dong-hee Na wrote: > >> So I'm also a supporter of new communication tools. > > > > I agree with everything you've mentioned, Dong-hee. Need for good > > tool/system that addressed our evolving needs was one of the driver of > > this conversation. > > You still haven't explained why e.g. Zulip (which has a modern Web UI, a > very well-thought threading mechanism, several clients, many > integrations, is widely used, and is open source), doesn't « address our > evolving needs ». In other words, I see lots of vague complaining and > no concrete argument. > > Regards > > Antoine. > ___ > 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/G2YRB5OAUHVJ6ITAPJE76X76XO2AHFOK/ > Code of Conduct: https://www.python.org/psf/codeofconduct/ > ___ 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/VU3XLU73WDCIOQQMSY6ZLMOGLI34SDWX/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: core-dev chat
> * Does it have a good web-client experience MS teams look like provide the web client. > In case it's not clear, I'd *like* a chat-style community, but I'd > prefer it to be a little more "social". I agree that we need to be more social. I share my personal news with Victor and it would be great if I can share my personal news with other core devs :) I think that we can catch both of them if we choose any tools I suggested. For example, we can create a channel for that purpose, #freetalk, #personal_news, etc.. 2021년 5월 15일 (토) 오후 5:20, Paul Moore 님이 작성: > On Sat, 15 May 2021 at 03:14, Dong-hee Na wrote: > > > > Believe it or not, there are people who are not familiar with the IRC > culture. > > And those people are who enter the opensource culture after the 2010s. > > That period coincides with the growth of GitHub. > > > > So I'm also a supporter of new communication tools. > > Here the list below is my consideration. > [...] > > Those are all good points. I'll add one more: > > * Does it have a good web-client experience? Not everyone wants to run > an additional client, so being able to get the full client experience > in a browser tab is important. > > In case it's not clear, I'd *like* a chat-style community, but I'd > prefer it to be a little more "social". We have plenty of > "work-related" communication channels, but IMO we don't really have > anywhere that's the online equivalent of the workplace "hanging out > around the coffee machine" interactions (which are often very > productive work-related conversations, but can also be purely social). > > Paul > ___ 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/HFA5ULLS3WQDXW7CYWOIKG7GOIZMR3WJ/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: core-dev chat
Believe it or not, there are people who are not familiar with the IRC culture. And those people are who enter the opensource culture after the 2010s. That period coincides with the growth of GitHub. So I'm also a supporter of new communication tools. Here the list below is my consideration. a) Are people familiar? If the tools are widely used by the tech company, I'd like to give the score. Because if the people are not familiar, it loses accessibility and maybe nobody use after some period. b) Does it has a thread feature? I believe that most of the core devs need this feature since I observe that we discuss some topics intensively for long periods of time. c) Does it has a secret channel? d) Can we get a sponsor from the provider or PSF for using the tools. Because most of the tools have a subscription system and without that, we can not use the advanced features. For example, with free tier Slack, we lose old historical data. So here is final my preferred list of that consideration >>> ["Slack", "Discord", "Teams"] But my personal recent experience with the Discord public server was not that good. Because I got a lot of personal talks invitation that is actually spam or scam. So I exit the channel after the sprint is ended even though I use Discord personally. If we choose Discord, I'd like to suggest creating a new server for PSF, not the rendezvous with the existed server. This is the same opinion with Slack if we have the possibility to meet with the same issue. Regards, Dong-hee 2021년 5월 14일 (금) 오전 8:39, Senthil Kumaran 님이 작성: > Hello Core Dev, > > I find a need for a core-dev chat service, wherein I could engage in > some quick effervescent conversations. > > It is like a team chat, that is popular with remote work these days. > We even seem to have used Zoom Chat yesterday! > > * I know #python-dev in IRC exists, but it is mostly a channel for > bots to send notifications, and there are plenty. I am not certain if > any core dev is active there. There was a time when this was active. > * We tried python discord last year, and were bit overwhelmed with the > number of channels and inability to customize > * There seems to be Slack called pyslackers too[1]. I am yet to try it. > > To have a proper team-chat, we need a service (a) as well as (b) team > using that. > > Does anyone else feel the need? Should we explore any? My thoughts and > options are > > a) Resurrect #python-dev - changing notifications to different group. > b) Request for core-dev in pyslackers Slack > c) Request for core-dev in Discord. > > Any other ideas are welcome. > > If you think that chatting is not a good idea, and a mailing list, and > discourse(discuss.python.org) are the best option, please share your > thoughts as well. > > If we feel a chat service will be a good idea for core-dev to > hangaround, then we can go to stage 2 of choosing the service by votes > in discourse (discuss.python.org). > > > Thank you, > Senthil > ___ > 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/BVPITIYRECSGCX2JUTMT7F7CCCYQSK4K/ > Code of Conduct: https://www.python.org/psf/codeofconduct/ > ___ 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/KMPHL7FMPLADQ4CYLXO5DYAEYCXUIM6A/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Erlend Aasland is now a member of Python Triage team
Hi I am very happy to share that Erlend Aasland is now a member of the Python Triage team. https://github.com/python/core-workflow/issues/402 Erlend improved the sqlite3 module for the recent period and he shows notable knowledge about sqlite3. So I believe that his contribution will enhance the CPython project and I think that he is well deserved to get triage permission. I am very looking forward to his future work :) https://github.com/python/cpython/commits?author=erlend-aasland I am going to help his new responsibility like what I got from my mentor. Welcome, Erlend! And thanks to everyone who helps me with this process. (Especially for Mariatta, Victor, Ee, Zack, Stéphane) ___ 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/HDHWJZ4YQW747XPFG5SKGDOTQTEZTIAW/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: Hai Shi got the bug triage permission
Congratulations Hai Shi! I am looking forward to your future contributions! Dong-hee 2020년 11월 14일 (토) 오전 12:38, Victor Stinner 님이 작성: > Hi, > > I just gave the bug triage permission to Hai Shi. I will continue to > mentor him for his new responsibilities, as I already did through code > reviews last months. > > In 2020, he is the #5 most active developer and the #1 most active > non-core dev developer on the CPython project! > > He got 101 commits merged into the master branch. I'm working with him > on fixing the Python finalization (bpo-1635741), converting static > types to heap types (bpo-40077) and converting extension modules to > the multiphase initialization API (PEP 489). But he also fixed many > other issues. Hai Shi's commits: > https://github.com/python/cpython/commits?author=shihai1991 > > While I'm was able to give him the permission on bugs.python.org, I'm > still waiting for someone to give him the permission on GitHub as well > (to add labels on PRs): > https://github.com/python/core-workflow/issues/385 > > Note: Just to be clear, he only becomes a trigger, not a core dev ;-) > > I added him in CC in this email ;-) > > Congratulations Hai Shi! > > Victor > -- > Night gathers, and now my watch begins. It shall not end until my death. > ___ > 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/MLO4LWMOT5DW6JD7RCHDS5GPLNWHXCNE/ > Code of Conduct: https://www.python.org/psf/codeofconduct/ > ___ 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/5I6B2IWF2FC244EOIJZATLJFE32CPCTD/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: Welcome Batuhan Taskaya to the team!
Congrats!! 2020년 11월 10일 (화) 오전 7:02, Brett Cannon 님이 작성: > > ___ > 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/23C4CKSESDVFUVJCSZ4X3U7CUPUJKWUP/ > Code of Conduct: https://www.python.org/psf/codeofconduct/ > ___ 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/PE5MNA3EFHE5FATDD6FFD75GTGNTWG37/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: Thank you Larry Hastings!
Thank you, Larry!! All members will remember all your efforts to the Python! 2020년 10월 6일 (화) 오전 3:39, Barry Warsaw 님이 작성: > They say being a Python Release Manager is a thankless job, so the Python > Secret Underground (PSU), which emphatically does not exist, hereby > officially doesn’t thank Larry for his years of diligent service as the > Python 3.4 and 3.5 release manager. > > On the other hand, the Python Steering Council, Python Software > Foundation, and worldwide Python community, all of which emphatically *do* > exist, all extend our heartfelt thanks to Larry for his excellent > stewardship of Python 3.4 and 3.5! > > Python 3.4 and 3.5 were both pivotal releases. While the features of > these two releases are too numerous to mention here, they introduced such > staples as: > > * asyncio > * enum > * pathlib > * async and await keywords > * matrix multiplication operators > * typing and zipapp modules > > and so much more. For details, see: > > * https://docs.python.org/3/whatsnew/3.4.html > * https://docs.python.org/3/whatsnew/3.5.html > > Larry’s first official release of 3.4.0a1 was on 2013-08-03 and his last > Python 3.5.10 release was 2020-09-05. That’s 7 years of exemplary release > managing! > > Larry, from all of us, and from me personally, thank you so much for your > invaluable contributions to Python. Enjoy your retirement! > > Cheers, > -Barry (on behalf of the PSC and PSF) > > ___ > 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/QGIHFU64TBYT56K6M5A5LYTYTSVFKHWQ/ > Code of Conduct: https://www.python.org/psf/codeofconduct/ > -- Software Development Engineer at Kakao corp. Tel: +82 10-3353-9127 Email: donghee.n...@gmail.com | denn...@kakaocorp.com Linkedin: https://www.linkedin.com/in/dong-hee-na-2b713b49/ ___ 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/HKAEC425GVURTGHS4BGF23L3LDUXGHA2/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: Please welcome Lysandros Nikolaou to the team!
Welcome, Lysandros! and congrats! Thanks for your work on PEG parsers and I am also looking forward to your future work! Regards, Dong-hee 2020년 7월 1일 (수) 오전 9:35, Łukasz Langa 님이 작성: > > Welcome, Lysandros! Happy to see you here. > > - Ł > > > On 30 Jun 2020, at 21:21, Brett Cannon wrote: > > > > > > ___ > > 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/OQPA633CV5TA44BBYFBMU3CI4WRT4AVC/ > > Code of Conduct: https://www.python.org/psf/codeofconduct/ > ___ > 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/O53DYUPYMJVNRJI6R5DDXE64BBRBTZDB/ > Code of Conduct: https://www.python.org/psf/codeofconduct/ -- Software Development Engineer at Kakao corp. Tel: +82 010-3353-9127 Email: donghee.n...@gmail.com | denn...@kakaocorp.com Linkedin: https://www.linkedin.com/in/dong-hee-na-2b713b49/ ___ 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/4DN4DWKUXSXDTEVCWJSKHMYOMVEZIX7V/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: Welcome Kyle Stanley to the team!
Congrat Kyle! Welcome and I am looking forward to see you on language summit :) Regards, Dong-hee 2020년 4월 15일 (수) 오전 10:38, Kyle Stanley 님이 작성: > Thank you for the support everyone and for adding my permissions, Brett! I > wrote my "acceptance speech" over on discuss: > https://discuss.python.org/t/vote-to-promote-kyle-stanley/3839/7. > ___ > 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/SGXGL2YXL3EWXONMBJ4CZB37ZK6B5BPD/ > Code of Conduct: https://www.python.org/psf/codeofconduct/ > ___ 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/IDHQE26M7NIE3FCXTDASPUXXSFXLIQZ5/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: Welcome Dong-hee Na to the team!
> Nope, no need to wait. Me granting access came after the steering council > cleared your nomination. Thank you for the explanation :) 2020년 4월 10일 (금) 오전 2:06, Brett Cannon 님이 작성: > > Dong-hee Na wrote: > [SNIP] > > cc. > > If I had to wait for the announcement of the Steering Committee > > (https://discuss.python.org/t/vote-to-promote-dong-hee-na/3794/2 > > ) > > before writing this email, > > Thank you for your understanding in advance. > > Nope, no need to wait. Me granting access came after the steering council > cleared your nomination. > ___ > 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/BHOJWJ5LAKQ3ORBWE6ANRWNLUBMPDTO3/ > Code of Conduct: https://www.python.org/psf/codeofconduct/ -- Software Development Engineer at Kakao corp. Tel: +82 010-3353-9127 Email: donghee.n...@gmail.com | denn...@kakaocorp.com Linkedin: https://www.linkedin.com/in/dong-hee-na-2b713b49/ ___ 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/53SZLSLDYGBKPIW7O4KXUOWBXGXIBCWA/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: Welcome Dong-hee Na to the team!
Thank you for your very warm welcome while the world struggles with COVID-19. And thank you all for your contributions to Python over the last 30 years. My first meeting with Python Core developer was Carol at the Python 2019 Sprint held in Seoul, Korea last year. And I still remember her kind explanation. I still don't know all the parts of Python interpreter/compiler. Also, I am not an expert on a particular module yet. But I think the core developers' votes are looking forward to my growth potential, and I will try to develop Python into a better language in line with your expectations. Also, I would like to express my sincere gratitude to Victor for recommending me a promotion as a core developer. Victor has been mentoring me since I was a member of Triage. I expect you to give me mentoring in the future. I thank him in advance for his continuous mentoring and contributions. And I'd like to thank all the other core developers who reviewed my patches, including Serhiy, Naoki-San, Yuri, and Pablo that I couldn't mention at all. Finally, Python is a language that has been well maintained and grown for more than 30 years, but it will continue to grow. I will do my best to make Python a greater language. Once again, thank you for your welcome and warmth. I look forward to meeting all of us safely in the near future. Thank you. Regards, Dong-hee cc. If I had to wait for the announcement of the Steering Committee (https://discuss.python.org/t/vote-to-promote-dong-hee-na/3794/2 ) before writing this email, Thank you for your understanding in advance. 2020년 4월 9일 (목) 오전 11:18, Karthikeyan 님이 작성: > > Congratulations Dong-hee Na. Welcome to the team :) > > Regards, > Karthikeyan S > > On Thu, Apr 9, 2020, 6:54 AM Brett Cannon wrote: >> >> Assuming I didn't botch anything, Dong-hee should be all set up! >> ___ >> 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/5ZZVHJHAEHT3DW5Q3X5S336KM5FE4B2C/ >> Code of Conduct: https://www.python.org/psf/codeofconduct/ > > ___ > 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/B7SACOAL66SNWF77JMFG7CN3LGSWO33Q/ > Code of Conduct: https://www.python.org/psf/codeofconduct/ -- Software Development Engineer at Kakao corp. Tel: +82 010-3353-9127 Email: donghee.n...@gmail.com | denn...@kakaocorp.com Linkedin: https://www.linkedin.com/in/dong-hee-na-2b713b49/ ___ 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/OG6YCLER7DOQ6M7TGTXZCSADO23BUQH3/ Code of Conduct: https://www.python.org/psf/codeofconduct/
