Re: [Python-Dev] [Python-checkins] cpython: Issue #24064: Property() docstrings are now writeable.
On 5/13/2015 4:10 AM, raymond.hettinger wrote:
https://hg.python.org/cpython/rev/1e8a768fa0a5
changeset: 96010:1e8a768fa0a5
user:Raymond Hettinger pyt...@rcn.com
date:Wed May 13 01:09:59 2015 -0700
summary:
Issue #24064: Property() docstrings are now writeable.
(Patch by Berker Peksag.)
diff --git a/Doc/library/collections.rst b/Doc/library/collections.rst
--- a/Doc/library/collections.rst
+++ b/Doc/library/collections.rst
@@ -924,6 +924,15 @@
Point3D = namedtuple('Point3D', Point._fields + ('z',))
+Docstrings can be customized by making direct assignments to the ``__doc__``
+fields:
+
+Book = namedtuple('Book', ['id', 'title', 'authors'])
+Book.__doc__ = 'Hardcover book in active collection'
+Book.id = '13-digit ISBN'
+Book.title = 'Title of first printing'
+Book.author = 'List of authors sorted by last name'
Should these be:
Book.id.__doc__ = ...
etc.?
+Point = namedtuple('Point', ['x', 'y'])
+Point.__doc__ = 'ordered pair'
+Point.x.__doc__ = 'abscissa'
+Point.y.__doc__ = 'ordinate'
These lines from /Doc/whatsnew/3.5.rst would make me think so.
Eric.
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-checkins] cpython: Issue #24064: Property() docstrings are now writeable.
On Wed, May 13, 2015 at 11:56 AM, Eric V. Smith e...@trueblade.com wrote:
On 5/13/2015 4:10 AM, raymond.hettinger wrote:
https://hg.python.org/cpython/rev/1e8a768fa0a5
changeset: 96010:1e8a768fa0a5
user:Raymond Hettinger pyt...@rcn.com
date:Wed May 13 01:09:59 2015 -0700
summary:
Issue #24064: Property() docstrings are now writeable.
(Patch by Berker Peksag.)
diff --git a/Doc/library/collections.rst b/Doc/library/collections.rst
--- a/Doc/library/collections.rst
+++ b/Doc/library/collections.rst
@@ -924,6 +924,15 @@
Point3D = namedtuple('Point3D', Point._fields + ('z',))
+Docstrings can be customized by making direct assignments to the ``__doc__``
+fields:
+
+Book = namedtuple('Book', ['id', 'title', 'authors'])
+Book.__doc__ = 'Hardcover book in active collection'
+Book.id = '13-digit ISBN'
+Book.title = 'Title of first printing'
+Book.author = 'List of authors sorted by last name'
Should these be:
Book.id.__doc__ = ...
etc.?
Hi Eric,
Good catch. Fixed in https://hg.python.org/cpython/rev/bde652ae05fd
Thanks!
--Berker
+Point = namedtuple('Point', ['x', 'y'])
+Point.__doc__ = 'ordered pair'
+Point.x.__doc__ = 'abscissa'
+Point.y.__doc__ = 'ordinate'
These lines from /Doc/whatsnew/3.5.rst would make me think so.
Eric.
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/berker.peksag%40gmail.com
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] cpython: Issue #20172: Convert the winsound module to Argument Clinic.
On Wed, May 13, 2015 at 1:50 AM, Serhiy Storchaka storch...@gmail.com wrote:
On 13.05.15 09:32, zach.ware wrote:
https://hg.python.org/cpython/rev/d3582826d24c
changeset: 96006:d3582826d24c
user:Zachary Ware zachary.w...@gmail.com
date:Wed May 13 01:21:21 2015 -0500
summary:
Issue #20172: Convert the winsound module to Argument Clinic.
+/*[clinic input]
+winsound.PlaySound
+
+sound: Py_UNICODE(nullable=True)
I think this is no longer correct syntax. Should be Py_UNICODE(accept={str,
NoneType}).
Oh, whoops. I forgot to run clinic over things again before committing.
We need to stick that into the Windows build process somewhere...
--
Zach
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Repository builds as 2.7.8+
Python 2.7.8+ (default, May 13 2015, 16:46:29) [MSC v.1500 32 bit (Intel)] on win32 Shouldn't this be 2.7.9+ or 2.7.10rc1? -- Terry Jan Reedy ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Repository builds as 2.7.8+
On Wed, May 13, 2015 at 4:05 PM, Terry Reedy tjre...@udel.edu wrote: Python 2.7.8+ (default, May 13 2015, 16:46:29) [MSC v.1500 32 bit (Intel)] on win32 Shouldn't this be 2.7.9+ or 2.7.10rc1? Make sure your repository is up to date, the patchlevel is correct at the current tip of the 2.7 branch. -- Zach ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Repository builds as 2.7.8+
On 5/13/2015 6:22 PM, Antoine Pitrou wrote: On Wed, 13 May 2015 18:15:10 -0400 Terry Reedy tjre...@udel.edu wrote: On 5/13/2015 5:45 PM, Zachary Ware wrote: On Wed, May 13, 2015 at 4:05 PM, Terry Reedy tjre...@udel.edu wrote: Python 2.7.8+ (default, May 13 2015, 16:46:29) [MSC v.1500 32 bit (Intel)] on win32 Shouldn't this be 2.7.9+ or 2.7.10rc1? Make sure your repository is up to date, the patchlevel is correct at the current tip of the 2.7 branch. I had just installed tortoise/hg 3.4, pulled and updated twice. Then ran external.bat on all branches. 2.7 tip is Kuchling's push at 15:25 utc What does hg sum say? F:\Python\dev\27hg sum parent: 96026:68d653f9a2c9 #19934: fix mangled wording branch: 2.7 commit: 6 modified update: (current) -- Terry Jan Reedy ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Repository builds as 2.7.8+
On 5/13/2015 5:45 PM, Zachary Ware wrote: On Wed, May 13, 2015 at 4:05 PM, Terry Reedy tjre...@udel.edu wrote: Python 2.7.8+ (default, May 13 2015, 16:46:29) [MSC v.1500 32 bit (Intel)] on win32 Shouldn't this be 2.7.9+ or 2.7.10rc1? Make sure your repository is up to date, the patchlevel is correct at the current tip of the 2.7 branch. I had just installed tortoise/hg 3.4, pulled and updated twice. Then ran external.bat on all branches. 2.7 tip is Kuchling's push at 15:25 utc I deleted python_d.exe and rebuilt it. External timestamp in Explorer is updated, internal one displayed on startup is not. The only changes in my working directory are to idle files. -- Terry Jan Reedy ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Repository builds as 2.7.8+
On Wed, 13 May 2015 18:15:10 -0400 Terry Reedy tjre...@udel.edu wrote: On 5/13/2015 5:45 PM, Zachary Ware wrote: On Wed, May 13, 2015 at 4:05 PM, Terry Reedy tjre...@udel.edu wrote: Python 2.7.8+ (default, May 13 2015, 16:46:29) [MSC v.1500 32 bit (Intel)] on win32 Shouldn't this be 2.7.9+ or 2.7.10rc1? Make sure your repository is up to date, the patchlevel is correct at the current tip of the 2.7 branch. I had just installed tortoise/hg 3.4, pulled and updated twice. Then ran external.bat on all branches. 2.7 tip is Kuchling's push at 15:25 utc What does hg sum say? ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Fwd: [docs] Python documentation missing
Hello, this happens every time we cut a RC release: the files referenced in the download section are missing and (rightfully so) people complain -- Forwarded message -- From: Ronald Legere rjl...@gmail.com Date: Wed, May 13, 2015 at 11:14 AM Subject: [docs] Python documentation missing To: d...@python.org The links to the downloadable documentation for python 2.7 are 404 on this page: https://docs.python.org/2/download.html Are they available somewhere -- Ron Legere (rjl...@gmail.com) C'est le temps que tu as perdu pour ta rose qui fait ta rose si importante ___ docs mailing list d...@python.org https://mail.python.org/mailman/listinfo/docs -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Fwd: [docs] Python documentation missing
On Wed, May 13, 2015, at 13:22, Sandro Tosi wrote: Hello, this happens every time we cut a RC release: the files referenced in the download section are missing and (rightfully so) people complain In this case, it was because the Python 3.5 docs were failing to build. Should be fixed in ~12 hours. ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Fwd: [docs] Python documentation missing
On Wed, May 13, 2015 at 1:36 PM, Benjamin Peterson benja...@python.org wrote: On Wed, May 13, 2015, at 13:22, Sandro Tosi wrote: Hello, this happens every time we cut a RC release: the files referenced in the download section are missing and (rightfully so) people complain In this case, it was because the Python 3.5 docs were failing to build. Should be fixed in ~12 hours. awesome! that was also a sort of heads up that it has happened regularly in the past (I can remember for sure since last summer at least) that cutting a RC release broke the doc download Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] cpython: Issue #20172: Convert the winsound module to Argument Clinic.
On 13.05.15 09:32, zach.ware wrote:
https://hg.python.org/cpython/rev/d3582826d24c
changeset: 96006:d3582826d24c
user:Zachary Ware zachary.w...@gmail.com
date:Wed May 13 01:21:21 2015 -0500
summary:
Issue #20172: Convert the winsound module to Argument Clinic.
+/*[clinic input]
+winsound.PlaySound
+
+sound: Py_UNICODE(nullable=True)
I think this is no longer correct syntax. Should be
Py_UNICODE(accept={str, NoneType}).
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)
On Tue, May 12, 2015 at 8:04 PM, Larry Hastings la...@hastings.org wrote: What do you think? My votes are as follows: Workflow 0: -0.5 Workflow 1: +1 Workflow 2: +0.5 Please cast your votes, Workflow 0: -0 Workflow 1: +1 Workflow 2: +0 --Berker ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)
On 05/12/2015 05:19 PM, Nick Coghlan wrote: Workflow 0: -0 Workflow 1: +1 Workflow 2: +0 That's taking into account the clarification that the buildbots will be set up to track the 3.5.x branch after the beta is forked, and that Larry will also push the 3.5rcX repo to hg.python.org http://hg.python.org for branch testing. I sort of assumed the buildbots would start building the 3.5 branch once it was created, yes. (Are there any branches in the cpython repo that they ignore?) When you say branch testing, you mean running the buildbots against it? Right now the UI for doing that is pretty clunky. Kicking off a build against a server-side clone (iirc) requires clicking through a couple web pages, filling out a form, and clicking on a teeny-tiny button. It would help *tremendously* here if I could get this automated, so I could run a script locally that made everything happen. Is there a remote API for starting builds? Or existing automation of any kind? Who should I talk to about this stuff? (Possible alternative plan for the latter: rc1 isn't until August, and I could aim to have a pilot Kallithea instance set up by then that uses bugs.python.org http://bugs.python.org credentials to log in. If we didn't get that up and running for some reason, BitBucket could still be a fallback plan) I'm happy to consider it. My proposed workflow is only using a very small set of features, and I gather Kallithea already has those features. Bolting on authentication from bugs.python.org would make it *less* friction than using Bitbucket. But I couldn't say for sure until I got to try it. So get cracking, Nick! //arry/ ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
