Carol Willing added the comment:
Hi aroberge,
Thanks for filing this issue.
I'm triaging all of the open 'turtle' issues. I'm closing this issue since
introducing this suggested change would impact teaching materials and resources
that have already been published. Th
Carol Willing added the comment:
Hi @terry.reedy,
I'm triaging open "turtle" issues. What do you think would be a reasonable next
step for this issue? Perhaps: a contributor runs the demo and reports back here
with the current behavior experienced.
--
Carol Willing added the comment:
A good next step with this issue would be to look at the languages mentioned in
the devguide experts page
(https://devguide.python.org/experts/#documentation-translations) with people
interested in translations
--
nosy: +willingc
Change by Carol Willing :
--
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue27461>
___
___
Python-bugs-list mailing list
Unsubscrib
Change by Carol Willing :
--
stage: -> needs patch
___
Python tracker
<https://bugs.python.org/issue26571>
___
___
Python-bugs-list mailing list
Unsubscrib
Carol Willing added the comment:
The next action for this issue would be to run the demo listed on Python 3.7
and report the results back here. We can then document expected behavior if it
differs.
--
nosy: +willingc
___
Python tracker
<ht
Carol Willing added the comment:
I've updated the issue title to reflect Terry's comments and changed the stage
to needs patch.
--
nosy: +willingc
stage: test needed -> needs patch
title: turtle.py and turtledemo use the default tkinter icon -> Refactor icon
setti
Carol Willing added the comment:
Hi Rick,
I'm closing this issue as not reproducible. Thanks for filing it and using
Turtle.
--
nosy: +willingc
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python t
Carol Willing added the comment:
I think your suggestion for Brython and Skulpt is excellent. I believe that
it's important to point out that Python can be used client-side, and both your
suggestions have been around for a while, are stable, and often used in large
courses such as Op
Carol Willing added the comment:
Reopened at the request of the original submitter.
--
resolution: remind ->
stage: resolved -> patch review
status: closed -> open
___
Python tracker
<https://bugs.python.or
Change by Carol Willing :
--
pull_requests: +8664
___
Python tracker
<https://bugs.python.org/issue33649>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Carol Willing :
--
pull_requests: +8666
___
Python tracker
<https://bugs.python.org/issue33649>
___
___
Python-bugs-list mailing list
Unsubscribe:
Carol Willing added the comment:
Closing as the release has reached EOL.
--
nosy: +willingc
resolution: -> out of date
stage: needs patch -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.o
Change by Carol Willing :
--
pull_requests: +8704
___
Python tracker
<https://bugs.python.org/issue33649>
___
___
Python-bugs-list mailing list
Unsubscribe:
Carol Willing added the comment:
Thank you for filing an issue. I will be carefully reviewing the Python
documentation section by section over the next several months. I will open
individual issues as I go through each section as well as pull requests as I
thoughtfully review each section
New submission from Carol Willing :
This issue is a placeholder for a comprehensive documentation review by content
sections. I will develop a more detailed workplan in the coming weeks.
--
assignee: willingc
messages: 325292
nosy: willingc
priority: normal
severity: normal
status
Change by Carol Willing :
--
pull_requests: +8715
___
Python tracker
<https://bugs.python.org/issue33649>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Carol Willing :
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue34678>
___
___
Change by Carol Willing :
--
pull_requests: +8735
___
Python tracker
<https://bugs.python.org/issue33649>
___
___
Python-bugs-list mailing list
Unsubscribe:
Carol Willing added the comment:
New changeset c9d66f0ed4f07b9d184d22abbfdd4c3c8e2702df by Carol Willing in
branch 'master':
bpo-33649 Polish asyncio docs on queues, protocols, and subproccesses (#9306)
https://github.com/python/cpython/commit/c9d66f0ed4f07b9d184d22abbfdd4c
Carol Willing added the comment:
New changeset 3faaa8857a42a36383bb18425444e597fc876797 by Carol Willing (Yury
Selivanov) in branch 'master':
bpo-33649: Refresh Tasks and Futures pages (#9314)
https://github.com/python/cpython/commit/3faaa8857a42a36383bb18425444e5
Change by Carol Willing :
--
nosy: +willingc
stage: test needed -> patch review
___
Python tracker
<https://bugs.python.org/issue29883>
___
___
Python-bugs-lis
Carol Willing added the comment:
Hi all,
I'm going to close this issue for now. As I mentioned earlier (sorry Terry for
not being clearer), I will be doing a comprehensive review of the docs and
source code over the next few months. I will make recommendations as PRs and
issues as
Carol Willing added the comment:
Confirming that I see the same behavior as reported by @xtreak.
--
nosy: +willingc
stage: -> needs patch
versions: +Python 3.7
___
Python tracker
<https://bugs.python.org/issu
Carol Willing added the comment:
@mdk The asyncio folks did make a change to the layout in
https://github.com/python/cpython/pull/9364 . It's a bit weird that 3.7 is the
release that is missing the search bar.
--
___
Python tracker
&
Carol Willing added the comment:
Does master and 3.7 branch build the docs at different times? It's odd to me
that master still shows the search box and 3.7 does not.
I'm getting on a flight soon. Yury would be a good person to ping re
Carol Willing added the comment:
New changeset 558c49bcf3a8543d64a68de836b5d855efd56696 by Carol Willing (João
Júnior) in branch 'master':
bpo-34728: Remove deprecate *loop* argument in asyncio.sleep (GH-9415)
https://github.com/python/cpython/commit/558c49bcf3a8543d64a68de836b5d8
Change by Carol Willing :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Carol Willing added the comment:
New changeset ffc5a14d00db984c8e72c7b67da8a493e17e2c14 by Carol Willing (Sanyam
Khurana) in branch 'master':
bpo-33014: Clarify str.isidentifier docstring (GH-6088)
https://github.com/python/cpython/commit/ffc5a14d00db984c8e72c7b67da8a4
Carol Willing added the comment:
Updated documentation using Terry Reedy's suggested addition.
--
nosy: +willingc
Added file: http://bugs.python.org/file35069/issue21026.patch
___
Python tracker
<http://bugs.python.org/is
Carol Willing added the comment:
Looks as if there is a patch for this on Issue 20064.
http://bugs.python.org/issue20064
--
nosy: +willingc
___
Python tracker
<http://bugs.python.org/issue18
Carol Willing added the comment:
I've reviewed this patch. It's my first patch review for this project so I'm
not sure that I submitted the review correctly in Rietveld.
--
nosy: +willingc
___
Python tracker
<http://bugs.pyt
New submission from Carol Willing:
As reported by a couple of users on the python-docs mailing list:
Python 3.4.2rc1 docs are giving a 404 Not Found when clicking on the links to
download (https://docs.python.org/3.4/download.html).
Python 3.5.0a0 links download docs correctly
(https
Carol Willing added the comment:
Thanks Berker. I'm glad it's being addressed and you have submitted a patch.
--
___
Python tracker
<http://bugs.python.o
Carol Willing added the comment:
Another report of sqlite3 not compiling correctly on RHEL6
(https://github.com/jupyterhub/jupyterhub/issues/991). Is there currently a
solution to build Python 3.6 with sqlite3 support?
--
nosy: +willingc
___
Python
Changes by Carol Willing :
--
stage: needs patch -> patch review
___
Python tracker
<http://bugs.python.org/issue8232>
___
___
Python-bugs-list mailing list
Un
Carol Willing added the comment:
After Ned's last message, perhaps it would be best to close this issue.
--
nosy: +willingc
___
Python tracker
<http://bugs.python.org/is
Carol Willing added the comment:
This issue is languishing. Recommend closing the issue.
--
nosy: +willingc
___
Python tracker
<http://bugs.python.org/issue8
Changes by Carol Willing :
--
resolution: -> out of date
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue8406>
___
___
Python-bugs-
Carol Willing added the comment:
Closing this out of date issue.
--
nosy: +willingc
resolution: -> out of date
status: open -> closed
___
Python tracker
<http://bugs.python.org/i
Carol Willing added the comment:
As per Ronald's last comment "close this as a duplicate of #16575 as that
better explains the underlying problem".
Closing this dated and duplicate issue.
--
components: +Benchmarks -Macintosh, ctypes
nosy: +brett.cannon, pitrou, will
Carol Willing added the comment:
Closed as an out of date issue.
--
nosy: +willingc
resolution: -> out of date
status: open -> closed
___
Python tracker
<http://bugs.python.org/i
Carol Willing added the comment:
Closed as an out of date issue.
--
nosy: +willingc
resolution: -> out of date
status: open -> closed
___
Python tracker
<http://bugs.python.org/
Carol Willing added the comment:
Closed as an out of date issue.
--
nosy: +willingc
resolution: -> out of date
status: open -> closed
___
Python tracker
<http://bugs.python.org/i
Carol Willing added the comment:
Ned, Closing as an out of date issue.
--
nosy: +willingc
resolution: -> out of date
status: open -> closed
___
Python tracker
<http://bugs.python.org/i
Carol Willing added the comment:
Closing as an out of date issue (greater than 2 years old).
--
nosy: +willingc
resolution: -> out of date
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.or
Carol Willing added the comment:
This issue was closed as "out of date" since there has been no activity on the
issue in 7 years.
IMHO the issue, if still relevant, should be opened as a new issue with better
scope based on today&#x
Carol Willing added the comment:
Perhaps it would be prudent to update the dev guide, or the contribution
process, to close issues that have stagnated for years as opposed to marking
them languishing. It would likely help with the issue backlog.
Also, expanding out of date to reflect that an
Carol Willing added the comment:
R. David, I'm confused. There isn't anything actionable from a development
standpoint on this issue. Why wouldn't it be marked languishing.
--
___
Python tracker
<http://bugs.pyt
Carol Willing added the comment:
R. David, Fair enough. Thanks for pointing out the difference between 'out of
date' and 'works for me'.
--
___
Python tracker
<http://bug
Carol Willing added the comment:
R. David, Would there be a better resolution than 'out of date'? The other
resolutions didn't really seem to fit either.
Agree, that the issue is a moot point.
--
___
Python tracker
<http
Carol Willing added the comment:
Lisa, thanks for your work and persistence on this patch. In particular, the
pydoctheme's sidebar improves the user's ability to navigate through the
devguide's content. Thank you!
If folks desire more distinction between the devguide and th
Carol Willing added the comment:
Ronald, while I may have closed this issue prematurely in other folks' view, I
did not do so without thought or reflecting if the issue was relevant.
My recommendation to close the issue was based on several factors:
- the desire to assist triaging issues
Carol Willing added the comment:
Fair enough.
Ronald and David, I respect your suggestions and thoughts, and I will not
triage or close old issues. FWIW, I was trying to be helpful. We regularly
close issues that are 1+ year old on Jupyter/IPython or rescope the issue to be
actionable for
Carol Willing added the comment:
@amylou Thank you for submitting this documentation suggestion about the Python
Tutorial.
This tutorial section, 4.7.1 Default Argument Values, tries to show that a
function can have multiple input arguments which may be given default values.
While the
Carol Willing added the comment:
FWIW: On Mac OS X 10.9.5 using Python 3.4.2, IDLE's interactive shell (started
from the IDLE.app icon):
>>>print('hello\b\b\b\b\bHELLO')
helloHELLO
>From the command line using python3 interactive shell:
>>>print('he
Carol Willing added the comment:
Ned, Thanks for the detailed example and confirming my gut instinct that Tk was
the root cause of the differences seen between the IDLE's Python interactive
shell (https://docs.python.org/3.4/library/idle.html) and the interactive
interpreter invoked fro
Carol Willing added the comment:
Alan, Thanks for reporting your issue. I have spent some time looking at it,
and I have triaged it as best as I am able for the other developers and you. I
am editing the issue title for clarity.
The issue is related to nonblocking i/o between a '
Carol Willing added the comment:
Current version
Each virtual environment has its own Python binary (allowing creation of
environments with various Python versions) and can have its own independent set
of installed Python packages in its site directories.
Another suggested revision
Since its
Carol Willing added the comment:
David,
Sounds good to me. I'll submit a patch with Graham's suggested text and move
the See also box up right after the PEP reference.
Thanks,
Carol
--
___
Python tracker
<http://bugs.python.o
Carol Willing added the comment:
Thank you R. David and Zach. The patch looks good to me too, and the info will
be helpful to others.
Please commit and let's get this good info out to others :)
(I don't have privileges or I would do so.)
--
stage: patch review ->
Carol Willing added the comment:
R. David, this will be an excellent addition to the devguide. Great clarity in
the text. I particularly like your discussion of what are buildbots and who
provides and maintains them. It also encourages those interested in a
particular os to consider
Carol Willing added the comment:
Closing this issue since a newer issue #24440 addresses devguide documentation
of installing and running a buildbot. Thanks to R. David Murray for submitting
the patch to #24440.
--
nosy: +willingc
resolution: -> duplicate
stage: patch rev
New submission from Carol Willing:
Add a Quick Start: Communications section to devguide (or Q S: Community
Interaction) as discussed on python-dev mailing list today.
The Quick Start: Communications section should be brief, link to other sections
in the devguide, and give contributor&#
Carol Willing added the comment:
Ezio, thanks for the suggestions :D
To clarify, the new Quick Start will be:
- brief;
- contain links to additional communication/community interaction info in the
devguide;
- guide a new contributor (or remind others) to information about ways to
Carol Willing added the comment:
Here's the patch for adding the `Quick Start: Community workflow` section to
the devguide.
I made a few other minor edits to the index page (replacing beginner/advanced
wording for starter/additional) since docs and testing are important. While
doc
New submission from Carol Willing:
To keep the scope of issue<24682> focused on the Quick Start sections of the
devguide, I am creating this issue to add a new subsection 12.4 ("Tips for
effective online communication") to devguide/communication.
The following are suggesti
Carol Willing added the comment:
Thanks Stephen for the additional links and suggestions.
I would like to keep this issue focused on the Quick Start section added in the
patch.
I've opened Issue<24689> to focus on "tips for effective online communication".
I have re
Carol Willing added the comment:
Ezio and Stephen, The "content" that you are brainstorming here is very
helpful, and I'm learning new resources and detail from it.
I've learned something from Ezio's link to Nick's post on python-committers.
I'm not a core
Carol Willing added the comment:
I reviewed the patch for this issue, and it looks ready to commit. If one of
the core devs could do the commit review/merge, we can close out this issue :)
Thanks Paul for your contribution. The patch looks good. As a tip for the
future, it's helpful i
Carol Willing added the comment:
Thanks Berker for the commit review.
Paul Anton Letnes, thanks for your contribution to the devguide. Nicely done.
--
___
Python tracker
<http://bugs.python.org/issue10
Carol Willing added the comment:
Biwan John, thanks for the issue report.
I can confirm that there is jitter due to scroll speed lag in Chrome for Python
2.7 docs. This behavior does not happen with Python 3.x docs. No issues with
Firefox.
I am using Mac OS X 10.10 with up-to-date Chrome and
Carol Willing added the comment:
Berker, Thanks for restaging this issue. I have attached a patch which
implements your suggested approach. If you have time to review and commit, I
would appreciate the help.
--
stage: needs patch -> patch review
Added file: http://bugs.python.
Carol Willing added the comment:
Updated patch to include Steve Dower's feedback.
--
Added file: http://bugs.python.org/file40043/iss17570v2.patch
___
Python tracker
<http://bugs.python.org/is
Carol Willing added the comment:
Using Ned Deily's feedback, I have added a devguide patch to clarify that 'make
touch' only works with a Mercurial clone and was not designed for git clones.
This patch, iss23404devguide.patch, resolves the devguide portion of this issue
un
Carol Willing added the comment:
I've reviewed doc19316.patch. Unfortunately, the patch does not apply cleanly
to the up-to-date codebase; it emits this error:
```
patching file compiler.rst
Hunk #1 succeeded at 41 with fuzz 2.
Hunk #3 succeeded at 175 (offset 6 lines).
patch: malf
Carol Willing added the comment:
@acucci and R. David Murray: I've run the patch locally, and all renders well
except for one link.
@acucci: I believe that the direct link to the `open()` command should be
... "see :func:`open` "
An example exists at the beginning of the sec
Carol Willing added the comment:
Steve and Zach, If you are happy with the changes, I have no objection to
committing and closing this issue.
--
___
Python tracker
<http://bugs.python.org/issue17
Carol Willing added the comment:
Is the behavior different in default or 3.5 release and 2.7 release?
The default branch has html_theme in Doc/conf.py
https://hg.python.org/cpython/file/default/Doc/conf.py set to 'pydoctheme'.
The 2.7 branch has html_theme in Doc/conf
Carol Willing added the comment:
David, Thanks for pointing this out. I totally forgot that the 2 and 3 versions
use different themes :(
--
___
Python tracker
<http://bugs.python.org/issue24
Carol Willing added the comment:
This looks great. Two very minor typos. Overall, the patch renders nicely and
can be merged. I agree that it is worth merging with or without windows
instructions (which may be added later).
Missing 'd' in email address
+python-builsb...@python.org
Carol Willing added the comment:
Zach, Steve, Ezio: The latest patch is ready to be committed. Thanks.
--
stage: patch review -> commit review
___
Python tracker
<http://bugs.python.org/issu
Carol Willing added the comment:
Zach, Sorry for not comprehending your comment re: latest patch correctly.
Since Rietveld isn't available on devguide, which makes comparison of patches
difficult (at least for me), here's some proposed wording to see if I am
understanding yo
Carol Willing added the comment:
Thanks Zach :D Makes more sense now ;)
--
___
Python tracker
<http://bugs.python.org/issue17570>
___
___
Python-bugs-list mailin
Carol Willing added the comment:
The highlighting of code box extends beyond the bounds of the box to the far
right of the page. A screenshot is attached as an example. The behavior occurs
on all versions (3.2+, 2.7.x) except 2.6.
Thanks for reporting this issue.
--
nosy: +willingc
Carol Willing added the comment:
I am unable to pip install scipy, numpy, or pandas using 3.5.0 on OS X 10.10.4.
After installing Python 3.5 using the installer downloaded from Python.org
page, I created a virtualenv using `pyvenv myscipy` and activated with `source
myscipy\bin\activate
Carol Willing added the comment:
Naveen, I was able to resolve this problem for installation by installing
gfortran using the instructions here: http://hpc.sourceforge.net/
After gfortran is successfully installed, I was able to ``pip install scipy
-v`` the libraries that depend on gfortran
Carol Willing added the comment:
Although the documentation for Python 3 and Python 2 is correct as Martin
shared, adding a note about capitalization in the Python 3 docs would be
helpful for beginners for two reasons: 1) the name of the Tkinter project does
start with a capital 'T&#
Carol Willing added the comment:
Thank you Bar Harel for submitting a patch.
Ultimately, I believe that the wording should be what is most helpful for the
end users.
If you wish to avoid mentioning Python 2, then a simple note cautioning the
user to take care that the case of the module
Carol Willing added the comment:
+1 to adding the EOF info to the Docs front page and a link from the downloads
page.
Also, +1 to David's suggestion to adding the devguide as well to the front
page. In the future, it would be nice to add the devguide to the CPython repo
instead of havi
Carol Willing added the comment:
And that would be EOL (end of life) not EOF. More coffee please...
--
___
Python tracker
<http://bugs.python.org/issue25
Carol Willing added the comment:
Ezio, Brett, Stephen: Would one of you be able to merge this? Thanks.
--
___
Python tracker
<http://bugs.python.org/issue24
Carol Willing added the comment:
Stephen, Thanks for reviewing to make sure it's still current. I appreciate it.
Core devs: Please merge and we'll close this one. Thanks.
--
___
Python tracker
<http://bugs.python.o
Carol Willing added the comment:
R. David Murray wrote:
>
> R. David Murray added the comment:
>
> Carol: as part of requesting a commit you can set the stage to 'commit
> review' (I've done that for this one) and that may lead to at least a
> couple of
Carol Willing added the comment:
David, I love the three paragraph intro. It captures the essence of the dev
guide usage from newcomers to the project to experienced core devs. I really
like the second paragraph and how it suggests focusing on the issue at hand.
Thanks, and I will take these
Changes by Carol Willing :
--
nosy: +willingc
stage: needs patch -> patch review
___
Python tracker
<http://bugs.python.org/issue25567>
___
___
Python-bugs-lis
New submission from Carol Willing:
On Mac OSX 10.9.5, test_socket fails when regression tests are run.
Specifically, the following fails:
FAIL: test_host_resolution (test.test_socket.GeneralModuleTests)
--
Traceback (most
Carol Willing added the comment:
Thanks Ned and R. David. A few questions...
1. I've rerun the tests using:
One failure:
70 tests OK.
1 test failed:
test_socket
1 test altered the execution environment:
test_warnings
21 tests skipped:
test_curses test_dbm_gnu test_de
Changes by Carol Willing :
--
nosy: +willingc
___
Python tracker
<http://bugs.python.org/issue14218>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Carol Willing:
Since many devs use OS X, it would be helpful to add a mention of OS X in Step
2 (Build). It would also be helpful to add that it is okay to ignore build
errors/warnings as long as CPython reports building correctly.
--
components: Devguide
messages
101 - 200 of 244 matches
Mail list logo
