Mailman 3 May 2015 - Python-Dev

Repository builds as 2.7.8+
by Terry Reedy 13 May '15

13 May '15

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

3 4

Fwd: [docs] Python documentation missing
by Sandro Tosi 13 May '15

13 May '15

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 <rjljr2(a)gmail.com> Date: Wed, May 13, 2015 at 11:14 AM Subject: [docs] Python documentation missing To: docs(a)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 (rjljr2(a)gmail.com) C'est le temps que tu as perdu pour ta rose qui fait ta rose si importante _______________________________________________ docs mailing list docs(a)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

2 2

Re: [Python-Dev] cpython: Issue #20172: Convert the winsound module to Argument Clinic.
by Serhiy Storchaka 13 May '15

13 May '15

On 13.05.15 09:32, zach.ware wrote: > https://hg.python.org/cpython/rev/d3582826d24c > changeset: 96006:d3582826d24c > user: Zachary Ware <zachary.ware(a)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}).

2 1

Re: [Python-Dev] [Python-checkins] cpython: Issue #24064: Property() docstrings are now writeable.
by Eric V. Smith 13 May '15

13 May '15

On 5/13/2015 4:10 AM, raymond.hettinger wrote: > https://hg.python.org/cpython/rev/1e8a768fa0a5 > changeset: 96010:1e8a768fa0a5 > user: Raymond Hettinger <python(a)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.

2 1

Re: [Python-Dev] [python-committers] How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)
by Larry Hastings 13 May '15

13 May '15

On 05/12/2015 11:18 AM, Jesus Cea wrote: > Larry, could you comment about the impact in the buildbots?. I suppose > option #1 could allows us to test both 3.5 and 3.6 changes. Would you > confirm this? Workflow #1 gets us automatic buildbot testing for the 3.5 branch (betas and 3.5.1) and trunk (3.6). It doesn't get us testing of the 3.5.0 release candidates automatically, because those would be hosted at bitbucket. However: hg.python.org allows creating "server-side clones" which can manually run tests against the buildbots. So if I create a server-side clone, then push the release candidate branch there, I can kick off buildbot tests. Who knows, maybe I'd even automate that process. //arry/

1 0

Fwd: Coverity Scan update
by Guido van Rossum 12 May '15

12 May '15

---------- Forwarded message ---------- From: "Dakshesh Vyas" <dvyas(a)coverity.com> Date: May 12, 2015 1:08 AM Subject: Coverity Scan update To: "guido(a)python.org" <guido(a)python.org> Cc: Hello Guido van Rossum, Thank you for using Coverity Scan. With more than 4000 open source projects now registered at Coverity Scan, we are committed to help the open source community find quality and security issues early in development. We would like to inform you that you can now nominate your favorite defect! Tell us which defects you are glad were found using Coverity Scan and get special gifts like a Samsung Gear 2 Smartwatch, Code Black Drone or Tile for iOS and Android. Gifts will be distributed every month based on defect nomination! We recently added new hardware resource and upgraded our Scan server to our latest 7.6 version, which includes great new features: * New security and quality checkers with version 7.6. * You can now setup automatic approval for viewing defects in read-only mode for everyone. * See charts showing defects outstanding vs. fixed over a period of time, and sort high impact defects by category. * Support for standard SSL port 443 instead of 8443. * Subscribe to email notifications for your entire open source project or for specific components or modules within your project. * You can now submit builds more frequently. * Please download the latest Coverity Build tool from https://scan.coverity.com/download * The old Coverity Build tool will still continue to work, but it may not be able to find some security and quality defects that could be found using our new and improved checkers as a part of 7.6 upgrade. * Important note for projects that uses automation or a script to submit build to Coverity Scan: The old URL to upload build on scan5.coverity.com is no longer supported. It is applicable to and used by some of the old projects on Coverity Scan. * Please sign-in to Coverity Scan to find the updated URL under automation section of Submit Build. * Finally, don't forget to nominate your favorite defects to receive special gifts like a Samsung Gear 2 Smartwatch, Code Black Drone or Tile for iOS and Android every month! Post your technical questions at https://communities.coverity.com/community/scan-(open-source)/content Please email us at scan-admin(a)coverity.com if you have any question or concerns, and we would be happy to help you. Thanks Dakshesh Vyas | Technical Manager - Coverity Scan Office: 415.935.2957 | dvyas(a)coverity.com https://scan.coverity.com/ Coverity by Synopsys To manage Coverity Scan email notifications, click https://scan.coverity.com/subscriptions/edit?email=guido%40python.org&token…

2 1

Clarification of PEP 476 "opting out" section
by Nick Coghlan 12 May '15

12 May '15

Hi folks, This is just a note to highlight the fact that I tweaked the "Opting out" section in PEP 476 based on various discussions I've had over the past few months: https://hg.python.org/peps/rev/dfd96ee9d6a8 The notable changes: * the example monkeypatching code handles AttributeError when looking up "ssl._create_unverified_context", in order to accommodate older versions of Python that don't have PEP 476 implemented * new paragraph making it clearer that while the intended use case for the monkeypatching trick is as a workaround to handle environments where you *know* HTTPS certificate verification won't work properly (including explicit references to sitecustomize.py and Standard Operating Environments for Python), there's also a secondary use case in allowing applications to provide a system administrator controlled setting to globally disable certificate verification (hence the change to the example code) * new paragraph making it explicit that even though we've improved Python's default behaviour, particularly security sensitive applications should still provide their own context rather than relying on the defaults Regards, Nick. -- Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia

8 41

Re: [Python-Dev] anomaly
by Mark Rosenblitt-Janssen 12 May '15

12 May '15

In case the example given at the start of the thread wasn't interesting enough, it also works in the other direction: >>> class str(int): pass >>> str('2') 2 #<----- an integer!!! Mark

3 2

What's missing in PEP-484 (Type hints)
by Dima Tisnek 12 May '15

12 May '15

# Syntactic sugar "Beautiful is better than ugly, " thus nice syntax is needed. Current syntax is very mechanical. Syntactic sugar is needed on top of current PEP. # internal vs external @intify def foo() -> int: b = "42" return b # check 1 x = foo() // 2 # check 2 Does the return type apply to implementation (str) or decorated callable (int)? How can same annotation or a pair of annotations be used to: * validate return statement type * validate subsequent use * look reasonable in the source code # lambda Not mentioned in the PEP, omitted for convenience or is there a rationale? f = lambda x: None if x is None else str(x ** 2) Current syntax seems to preclude annotation of `x` due to colon. Current syntax sort of allows lamba return type annotation, but it's easy to confuse with `f`. # local variables Not mentioned in the PEP Non-trivial code could really use these. # global variables Not mentioned in the PEP Module-level globals are part of API, annotation is welcome. What is the syntax? # comprehensions [3 * x.data for x in foo if "bar" in x.type] Arguable, perhaps annotation is only needed on `foo` here, but then how complex comprehensions, e.g. below, the intermediate comprehension could use an annotation [xx for y in [...] if ...] # class attributes s = socket.socket(...) s.type, s.family, s.proto # int s.fileno # callable If annotations are only available for methods, it will lead to Java-style explicit getters and setters. Python language and data model prefers properties instead, thus annotations are needed on attributes. # plain data user1 = dict(id=123, # always int name="uuu", # always str ...) # other fields possible smth = [42, "xx", ...] (why not namedtuple? b/c extensible, mutable) At least one PHP IDE allows to annotate PDO. Perhaps it's just bad taste in Python? Or is there a valid use-case? # personal note I think it's amazing how much thought has already been put into this proposal. The foundation is pretty solid (per Guido talk). I am not at all opposed to software that infers types (like jedi), or reads user-specified types (like phpstorm and pep 484) and does something good with that. In fact I'm ambivalent to current proposal, standard and promise of better tools on one hand; narrow scope, debatable looks on the other. -- dima

4 6

Unicode literals in Python 2.7
by Adam Bartoš 12 May '15

12 May '15

Hello, is it possible to somehow tell Python 2.7 to compile a code entered in the interactive session with the flag PyCF_SOURCE_IS_UTF8 set? I'm considering adding support for Python 2 in my package ( https://github.com/Drekin/win-unicode-console) and I have run into the fact that when u"α" is entered in the interactive session, it results in u"\xce\xb1" rather than u"\u03b1". As this seems to be a highly specialized question, I'm asking it here. Regards, Drekin

10 23