Re: How to build stable 3.9 branch from fork and clone of cpython
On Tue, May 18, 2021 at 4:33 PM wrote: > > 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? > git checkout 3.9 That should switch you to the branch, replacing all the (tracked) files in the build directory with the corresponding files from 3.9. Be aware that most development is going to happen on the master branch (or the main branch, whichever one you have), and branches like 3.9 are going to get backported patches; so any change you're planning to contribute to 3.9 is going to need to work correctly on both branches. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
Re: How to build stable 3.9 branch from fork and clone of cpython
On 5/18/2021 3:00 AM, Chris Angelico wrote: On Tue, May 18, 2021 at 4:33 PM wrote: 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? git checkout 3.9 That should switch you to the branch, replacing all the (tracked) files in the build directory with the corresponding files from 3.9. Be aware that most development is going to happen on the master branch (or the main branch, whichever one you have), It should be 'main' for any python/??? repository. If one forked and cloned before the switch, one should rename 'master' to 'main' both locally and on the fork. Github has directions somewhere. It might provide them if one attempts a PR against 'master'. There may also be something in the devguide. The only time an initial contribution would be for 3.9 would be for a bug that only exists in 3.9, which is very rare. and branches like 3.9 are going to get backported patches; so any change you're planning to contribute to 3.9 is going to need to work correctly on both branches. It must be 'main' for any python/??? repository. The only time an initial contribution would be for 3.9 would be for a bug that only exists in 3.9, which is very rare. -- Terry Jan Reedy -- https://mail.python.org/mailman/listinfo/python-list
Re: Writers [Was: Re: Standarize TOML?]
On 2021-05-18, Michael F. Stemper wrote:
> On 17/05/2021 18.48, Terry Reedy wrote:
>> 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.
>
> If I'm parsing this correctly, python supports something called a
> "writer", which does not mean "somebody who writes python".
You are not parsing it correctly. Terry means that at least some
existing TOML modules for Python include facilities for outputting
("writing") TOML as well as reading it, and this makes choosing
between those modules more controversial as there are more subjective
opinions involved in the implementation of writing TOML as opposed to
only reading it.
--
https://mail.python.org/mailman/listinfo/python-list
Writers [Was: Re: Standarize TOML?]
On 17/05/2021 18.48, Terry Reedy wrote: 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. If I'm parsing this correctly, python supports something called a "writer", which does not mean "somebody who writes python". Since I've never heard of this[1], I searched on: python writer but got stuff about how to write python and how to use python to write to files. Assuming that there is a python construct called a writer, could somebody point me to somewhere that I could read up on them? [1] Well, I've used csv.DictWriter() which might be an instance. -- Michael F. Stemper Galatians 3:28 -- https://mail.python.org/mailman/listinfo/python-list
Re: Writers [Was: Re: Standarize TOML?]
On 18/05/2021 08.23, Jon Ribbens wrote:
On 2021-05-18, Michael F. Stemper wrote:
On 17/05/2021 18.48, Terry Reedy wrote:
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.
If I'm parsing this correctly, python supports something called a
"writer", which does not mean "somebody who writes python".
You are not parsing it correctly. Terry means that at least some
existing TOML modules for Python include facilities for outputting
("writing") TOML as well as reading it, and this makes choosing
between those modules more controversial as there are more subjective
opinions involved in the implementation of writing TOML as opposed to
only reading it.
Okay, thanks.
--
Michael F. Stemper
This post contains greater than 95% post-consumer bytes by weight.
--
https://mail.python.org/mailman/listinfo/python-list
Winpdb-reborn anomalies
I'm attempting to run winpdb-reborn, version 2.0.0.1, under MinGW. My first problem is that if I enter winpdb in the directory containing , winpdb can't find rpdb2.py. I assume this is due to some path problem, but I don't know how to fix it. My second problem occurs when I run winpdb from the /c/Python39/Lib/site-packages directory. The program runs correctly as far as I can tell, but it writes about 20-30 lines of what looks like debug information to the rpdb2 console window. The ourput starts with a get_namespace() call. It does this after each debug action (step over, step into, etc.) I haven't been able to find any way to turn off this output. Any suggestions greatly appreciated! Dick -- https://mail.python.org/mailman/listinfo/python-list
Re: Winpdb-reborn anomalies - workaround
In article , encore1 @cox.net says... > > I'm attempting to run winpdb-reborn, version 2.0.0.1, under MinGW. My > first problem is that if I enter winpdb in the directory > containing , winpdb can't find rpdb2.py. I assume this is due > to some path problem, but I don't know how to fix it. > > My second problem occurs when I run winpdb from the > /c/Python39/Lib/site-packages directory. The program runs correctly as > far as I can tell, but it writes about 20-30 lines of what looks like > debug information to the rpdb2 console window. The ourput starts with a > get_namespace() call. It does this > after each debug action (step over, step into, etc.) I haven't been able > to find any way to turn off this output. > > Any suggestions greatly appreciated! > > Dick I found the code that forces debug info to be printed. The tests against the debug flag were commented out so debug info was written unconditionally. In case someone needs it, the file is rpdb/utils.py; look for fDebug. This doesn't fix the path problem, but I can live with that. Dick -- https://mail.python.org/mailman/listinfo/python-list
