[issue23761] test_socket fails on Mac OSX 10.9.5

Carol Willing added the comment: Tests for current CPython version now pass on Mac OSX 10.9.5. Closing issue. -- resolution: -> not a bug status: open -> closed ___ Python tracker <http://bugs.python.org/i

[issue23931] Update DevGuide link in Quickstart Step 1

New submission from Carol Willing: Change Quickstart step 1 link to redirect to Section 1.1 Getting Started. Currently, it redirects to 1.1.2 Getting the Source Code. For developers coming from git, step 1.1.1 Version Control Setup would be helpful. Feedback from PyCon 2015 Sprints suggest

[issue23924] Add OS X to Dev Guide Quickstart build step

Carol Willing added the comment: @ned.deily Thanks for the feedback. I changed the text on the QuickStart build step #2 since it was not clear to some sprinters that UNIX included Mac OS X. I added link in the text to direct to the Build Dependencies section. Thanks for the suggestion

[issue23931] Update DevGuide link in Quickstart Step 1

Carol Willing added the comment: @ezio.melotti I've reviewed the second version of the patch and it links as you requested to 1.1.1. It is ready to be merged. Thanks ttz. -- ___ Python tracker <http://bugs.python.org/is

[issue23931] Update DevGuide link in Quickstart Step 1

Changes by Carol Willing : -- stage: -> commit review ___ Python tracker <http://bugs.python.org/issue23931> ___ ___ Python-bugs-list mailing list Unsubscrib

[issue23924] Add OS X to Dev Guide Quickstart build step

Carol Willing added the comment: @ned.deily Thanks for the review. Please push for me. Thanks :) -- ___ Python tracker <http://bugs.python.org/issue23924> ___ ___

[issue23931] Update DevGuide link in Quickstart Step 1

Carol Willing added the comment: @berker.peksag I think that new contributors (esp. those at the sprints) want to get started quickly. Many do not read the whole devguide before starting even though the devguide is really helpful. I like your suggested approach to keep the original link and

[issue21400] Code coverage documentation is out-of-date.

Carol Willing added the comment: Patch applies cleanly. The out of date link has been removed. +1 ready for a core dev to merge. -- nosy: +willingc stage: patch review -> commit review ___ Python tracker <http://bugs.python.org/issu

[issue21400] Code coverage documentation is out-of-date.

Carol Willing added the comment: Thanks Heather for filing the PSF contribution form as well as the patch. I hope you will continue improving Python's documentation in the future :) -- ___ Python tracker <http://bugs.python.org/is

[issue12652] Keep test.support docs out of the global docs index

Carol Willing added the comment: Reviewed the issue history during the PyCon sprints. Thanks to all for the thoughts on this issue. I am closing this issue since any additional actions on this subject would be best filed as a new issue. -- nosy: +willingc resolution: -> out of d

[issue16222] some terms not found by devguide's search box

Carol Willing added the comment: Reviewed this issue's history at PyCon sprint. The devguide now provides results if searched for 'server side' or 'clone'. This issue is resolved. If additional search terms are required in the index, it is recommended that a new iss

[issue19121] Documentation guidelines enhancements

Carol Willing added the comment: Thanks to all for the feedback. Since this issue covers a sufficiently broad set of thoughts, it would be better suited for a PEP. Closing this issue with the recommendation to submit a PEP if interested. -- nosy: +willingc resolution: -> not a

[issue19121] Documentation guidelines enhancements

Changes by Carol Willing : -- stage: -> resolved ___ Python tracker <http://bugs.python.org/issue19121> ___ ___ Python-bugs-list mailing list Unsubscrib

[issue16405] Explain how to set up the whitespace commit hook locally

Changes by Carol Willing : -- assignee: -> willingc nosy: +willingc ___ Python tracker <http://bugs.python.org/issue16405> ___ ___ Python-bugs-list mai

[issue16405] Explain how to set up the whitespace commit hook locally

Carol Willing added the comment: Adds whitespace checking hook setup information to Minimal Configuration section of devguide [1]. Patch is ready for review. [1] https://docs.python.org/devguide/committing.html#minimal-configuration -- keywords: +patch stage: needs patch -> pa

[issue17284] create mercurial section in devguide's committing.rst

Carol Willing added the comment: I've reviewed this issue at the PyCon sprint. While I agree that there are sections that new contributors might wish to skip over, I believe that there is content that would benefit contributors that are not yet core developers. Going forward we can t

[issue23951] Update devguide style to use a similar theme as Docs

New submission from Carol Willing: It would be helpful to update the conf.py file and dependencies to use a modified 'pydoctheme' for the devguide style. The benefits would be improved readability, a consistent look with the stdlib docs, and collapsible sidebars. Attached is a scree

[issue23951] Update devguide style to use a similar theme as Docs

Carol Willing added the comment: Zach, Good point. Perhaps a different highlight color across the top would be enough to indicate that "you are in the dev guide". -- ___ Python tracker <http://bugs.python.o

[issue16405] Explain how to set up the whitespace commit hook locally

Carol Willing added the comment: Ned, Thanks for the review and feedback. It seems reasonable to me to mention both the "pretxncommit" hook as well as the "commit" hook as well as your brief comments on the difference between the two. I'll make that change

[issue16405] Explain how to set up the whitespace commit hook locally

Carol Willing added the comment: Patch is ready for review. Ned's feedback on "pretxncommit" hook is added. -- Added file: http://bugs.python.org/file39031/iss-hooks-1.patch ___ Python tracker <http://bugs.pyt

[issue18041] mention issues with code churn in the devguide

Carol Willing added the comment: https://bugs.python.org/issue23320 provides more recent input on reflow of paragraphs. This newer issue should be consulted when creating a patch for this issue. Ideally, both issues should be able to be closed with the same patch. -- nosy: +willingc

[issue23320] devguide should mention rules about "paragraph reflow" in the documentation

Carol Willing added the comment: https://bugs.python.org/issue18041 also provides related insights. Ideally, a patch for this issue should address and close both issues. -- nosy: +willingc ___ Python tracker <http://bugs.python.org/issue23

[issue13472] devguide doesn’t list all build dependencies

Carol Willing added the comment: I agree with Jeff's recommendation that this issue is resolved by content already in the devguide's Build Dependencies[1]. Jeff, Thanks for helping close an old issue. [1] https://docs.python.org/devguide/setup.html#build-dependencies --

[issue10708] Misc/porting should be folded into the development FAQ or the devguide

Changes by Carol Willing : -- keywords: +easy nosy: +willingc ___ Python tracker <http://bugs.python.org/issue10708> ___ ___ Python-bugs-list mailing list Unsub

[issue16574] clarify policy on updates to final peps

Carol Willing added the comment: This patch should close this languishing devguide issue. This patch adds wording suggested by Terry Reedy re: pep documentation reference to section 7.4.5 Inline markup (https://docs.python.org/devguide/documenting.html#id3). The devguide covers the pep

[issue17475] Better doc on using python-gdb.py

Carol Willing added the comment: The current devguide on gdb (https://docs.python.org/devguide/gdb.html?highlight=gdb) satisfies this issue. I am marking this languishing issue as a duplicate and closing it. -- nosy: +willingc resolution: -> duplicate stage: patch review -> re

[issue17227] devguide: buggy heading numbers

Carol Willing added the comment: Correct Python Developer FAQ Section 28 to match the style of Section 27. Section numbers should now flow correctly in Sphinx. A section contents is displayed at the top of the section page for the user's convenience (especially since the FAQ questions

[issue16931] mention work-around to create diffs in default/non-git mode

Changes by Carol Willing : -- assignee: -> willingc nosy: +willingc ___ Python tracker <http://bugs.python.org/issue16931> ___ ___ Python-bugs-list mai

[issue16930] mention limitations and/or alternatives to hg graft

Changes by Carol Willing : -- assignee: -> willingc nosy: +willingc ___ Python tracker <http://bugs.python.org/issue16930> ___ ___ Python-bugs-list mai

[issue24005] Documentation Error: Extra line Break

Carol Willing added the comment: janonymous, Thanks for the contribution. I agree with George that this is not a bug. The whitespace exists for developer readability and maintainability of code. Here's a section from PEP8 about the use of whitespace (https://www.python.org/dev/peps/pep

[issue17227] devguide: buggy heading numbers

Carol Willing added the comment: Berker, Thanks for the patch review. I'm going to work with the folks at Sphinx project this week to see if the headings are fixed in a newer Sphinx version. If so, I will make the change here. If not, I will follow your recommendation to close and crea

[issue24005] Documentation Error: Extra line Break

Carol Willing added the comment: Tim, A good point re: the interpreter. I've attached an output from IPython interpreter. Georg, Given Tim's additional insight, I'm inclined to reopen the issue and review the patch as a positive change. Though not a bug, but as an enhancement

[issue24016] Add a Sprints organization/preparation section to devguide

New submission from Carol Willing: Based on feedback from the PyCon 2015 CPython sprints (thank you R. David Murray and all the CPython contributors there), a sprint organization section will be added to the devguide. Here are some suggested subtopics in the Sprints organization section

[issue16574] clarify policy on updates to final peps

Changes by Carol Willing : -- stage: patch review -> commit review ___ Python tracker <http://bugs.python.org/issue16574> ___ ___ Python-bugs-list mai

[issue17475] Better doc on using python-gdb.py

Changes by Carol Willing : -- status: open -> closed ___ Python tracker <http://bugs.python.org/issue17475> ___ ___ Python-bugs-list mailing list Unsubscrib

[issue17846] Building Python on Windows - Supplementary info

Carol Willing added the comment: Thank you kathweaver and others who worked on this issue. After reviewing the long history of this issue and the changes made to the Windows sections of the devguide, I am closing this issue. I recognize that Terry Reedy's final comment about isolated

[issue20851] Update devguide to cover testing from a tarball

Carol Willing added the comment: Brett, Is documentation for a testing a tarball dumped for an RC still needed? If so, are the following steps accurate? 1. Download tarball 2. Extract tarball into a directory tar -xzvf release.tar.gz 3. Change directory into release directory cd release

[issue17570] Improve devguide Windows instructions

Carol Willing added the comment: This patch addresses Ezio's original issue in msg185482 to improve the Windows instructions on the "committing" page of the devguide. I have tried to match the style of the "Getting Started" page when distinguishing UNIX (Mac OS

[issue10965] dev task of documenting undocumented APIs

Carol Willing added the comment: Add key points from linked email in msg126662 to documentation section of the devguide. * provide developers guidance on how to document undocumented APIs * when and how to use __all__ * include rules from the linked email * highlight "do no harm" t

[issue24204] string.strip() documentation is misleading

Carol Willing added the comment: Additional text added about stripping characters from the leading end and trailing end of the string. An additional example that illustrates the outer characters being stripped while the inner string characters, even though matching the chars set of characters

[issue24220] ast.Call signature changed

Carol Willing added the comment: Matthias, Did you wish to mark this issue for additional Documentation and as a behavior change request (warning of signature change until 3.6) in addition to Devguide? I've summarized below some info from researching Matthias' original message. I

[issue24220] ast.Call signature changed

Carol Willing added the comment: Thanks Berker for pointing out the WIP patch for issue 16544. Issue 16544 seems a better place than this issue for addressing the ast documentation. There does not seem to be any additional action items left on this issue so I recommend closing this issue and

[issue16544] Add external link to ast docs

Carol Willing added the comment: Matthias, I've added you to the nosy list for this ast doc enhancements issue. Reference: msg243484 on Issue 24220. -- nosy: +mbussonn, willingc versions: +Python 3.5 ___ Python tracker <http://bugs.py

[issue24204] string.strip() documentation is misleading

Carol Willing added the comment: Updated patch with Terry's suggested changes. Thanks Terry and Raymond for the review of the initial patch. -- Added file: http://bugs.python.org/file39476/iss24204b.patch ___ Python tracker <http://bugs.py

<    1   2   3