How to build stable 3.9 branch from fork and clone of cpython
I am following the "Getting Started" section of the Python Developers Guide, but when I build the first version to verify everything builds, it builds branch 3.11. If I want to build and contribute to branch 3.9, how do I set that up please? OS is Windows 10. I have, I believe, all the necessary tools for the build, since the 3.11 version did build and in a very minimal test does execute successfully after the build (responds to "-V" option with build information). TIA for your assistance. Peter -- https://mail.python.org/mailman/listinfo/python-list
Re: Standarize TOML?
On 5/17/2021 4:29 PM, Barry Scott wrote: On 15 May 2021, at 23:39, Jason C. McDonald wrote: During the Steering Committee presentation at PyCon, it was mentioned that no one has formally proposed TOML be added to the standard library (emphasis on formal). THe joke went forth that there would be a flood of proposals to that end. So, just to kick this off while the thought is still fresh in a bunch of people's minds: **should we add a TOML parser to the standard library**? The main reason this matters is to help encourage adoption of the now PEP-standardized pyproject.toml. A few projects have cited the lack of a standardized TOML implementation in the standard library as a reason not to adopt pyproject.toml...and the topic thus became weirdly political. I understand that Brett Cannon intends to bring this up at the next language summit, but, ah, might as well put the community two-cents in now, hey? I, for one, feel like this is obvious. I think the python ideas list is a better place to have this discussion. I disagree. Rehashing *opinions* is pretty useless. The issues were already discussed on https://discuss.python.org/t/adopting-recommending-a-toml-parser/4068 There are multiple packages. There is no consensus on which to pick, *if any*. Existing modules apparently include writers, which are necessarily opinionated (as is formatting of C, Python, html, ...). As I just noted in the discussion, the stdlib does not have an html writer. So if we want just a parser, maybe we should generate one from the grammar. Then there are broader 'What should be in the stdlib discussions. If anyone has *new information* about toml, post it there. -- Terry Jan Reedy -- https://mail.python.org/mailman/listinfo/python-list
Re: Standarize TOML?
> On 15 May 2021, at 23:39, Jason C. McDonald wrote: > > During the Steering Committee presentation at PyCon, it was mentioned > that no one has formally proposed TOML be added to the standard library > (emphasis on formal). THe joke went forth that there would be a flood > of proposals to that end. > > So, just to kick this off while the thought is still fresh in a bunch of > people's minds: **should we add a TOML parser to the standard library**? > > The main reason this matters is to help encourage adoption of the now > PEP-standardized pyproject.toml. A few projects have cited the lack of > a standardized TOML implementation in the standard library as a reason > not to adopt pyproject.toml...and the topic thus became weirdly > political. > > I understand that Brett Cannon intends to bring this up at the next > language summit, but, ah, might as well put the community two-cents in > now, hey? > > I, for one, feel like this is obvious. I think the python ideas list is a better place to have this discussion. Barry > > -- > Jason C. McDonald (CodeMouse92) > Author | Speaker | Hacker | Time Lord > -- > https://mail.python.org/mailman/listinfo/python-list > -- https://mail.python.org/mailman/listinfo/python-list
Re: Standarize TOML?
Op 16-05-2021 om 00:39 schreef Jason C. McDonald: During the Steering Committee presentation at PyCon, it was mentioned that no one has formally proposed TOML be added to the standard library (emphasis on formal). THe joke went forth that there would be a flood of proposals to that end. So, just to kick this off while the thought is still fresh in a bunch of people's minds: **should we add a TOML parser to the standard library**? See here: https://discuss.python.org/t/adopting-recommending-a-toml-parser/4068 I, for one, feel like this is obvious. You are not the only one. The game is already on for some time. -- Met vriendelijke groet / Kind regards Menno Hölscher -- https://mail.python.org/mailman/listinfo/python-list
EuroPython 2021: Talk Voting is Open
Talk voting is your chance to tell us what you’d like to see at EuroPython 2021. We will leave talk voting open until: Sunday, May 23, 23:59:59 CEST In order to vote, please log in to the website and navigate to the talk voting page: * EuroPython 2021 Talk Voting * https://ep2021.europython.eu/events/talk-voting/ Who can participate? Any registered attendee of EuroPython 2021 with a paid ticket, as well as attendees of one of the past EuroPython conferences (going back to 2015) can vote. If you have submitted a proposal this year, you are also eligible to vote. If you have not attended EuroPython before, but want to participate in talk voting, you have to buy a ticket before you can vote: https://ep2021.europython.eu/registration/buy-tickets/ How talk voting works - The talk voting interface lists all submitted proposals, including talks, helpdesks and posters. You can then vote on the proposal you'd like to see at the event. Details on the voting process are described on our talk voting page. Talk Selection -- After the talk voting phase, the EuroPython Program Workgroup (WG) will use the votes to select the talks and build a schedule. The talk voting is a good and strong indicator of what attendees are interested to see. Submissions are also selected based on editorial criteria, for example, to increase diversity, give a chance to less mainstream topics and make sure that topics don't overlap too much. In general, the Program WG will try to give as many speakers a chance to talk as possible. If speakers have submitted multiple talks, the one with the highest rating will most likely get selected. Quick Summary - EuroPython 2021 will be run online from July 26 - August 1: - Two workshop/training days (July 26 - 27) - Three conference days (July 28 - 30) - Two sprint days (July 31 - August 1) The sessions will be scheduled to ensure they are also accessible for those in the Asian and Americas time zones. Help spread the word Please help us spread this message by sharing it on your social networks as widely as possible. Thank you ! Link to the blog post: https://blog.europython.eu/europython-2021-talk-voting-is-open/ Tweet: https://twitter.com/europython/status/1394245129083424768 Enjoy, -- EuroPython 2021 Team https://ep2021.europython.eu/ https://www.europython-society.org/ -- https://mail.python.org/mailman/listinfo/python-list
