On 11/02/2012 03:14, Eli Bendersky wrote:
On Sat, Feb 11, 2012 at 03:38, Jesse Nollerjnol...@gmail.com wrote:
I've been trying to publicize it on twitter, my blog, google plus and elsewhere.
help welcome.
It also appears in the first paragraph of Contributing in the dev
guide - which is
Eli, quite frankly no :(
The stock answer put it on the main page at python.org if actually
followed up in all cases would result in something unreadable, as the page
would be too noisy and displayed in something like Palatino size 1 (if there
is such a thing).
I'm just crossing my fingers
On Fri, 10 Feb 2012 16:06:15 +0200
Eli Bendersky eli...@gmail.com wrote:
Following the intensive and fruitful discussion of the (now rejected)
PEP 408
(http://mail.python.org/pipermail/python-dev/2012-January/115850.html),
we've drafted PEP 411 to summarize the conclusions with regards to
On Sat, Feb 11, 2012 at 04:32:56PM +1000, Nick Coghlan wrote:
This would then be seen by pydoc and help(), as well as being amenable
to programmatic inspection.
Would using
warnings.warn('This is a provisional API and may change radically from'
' release to release',
On Sat, 11 Feb 2012, Steven D'Aprano wrote:
Arguably, the canonical test for whether a package is provisional or not
should be the existence of __provisional__:
for package in packages:
if hasattr(package, '__provisional__')
assert package documentation includes boilerplate
Hello Mark,
I think the PEP should explain what happens when a keys table needs
resizing when setting an object's attribute.
Reading the implementation, it seems the sharing can disappear
definitely, which seems a bit worrying.
Regards
Antoine.
On Wed, 08 Feb 2012 19:18:14 +
Mark Shannon
On Fri, Feb 10, 2012 at 11:32 PM, Nick Coghlan ncogh...@gmail.com wrote:
On Sat, Feb 11, 2012 at 1:39 PM, Eric Snow ericsnowcurren...@gmail.com
wrote:
Is there more to it than having a simple __provisional__ attribute on
the module and/or a list at sys.provisional_modules?
Yes. As soon as
Antoine Pitrou wrote:
Hello Mark,
I think the PEP should explain what happens when a keys table needs
resizing when setting an object's attribute.
If the object is the only instance of a class, it remains split,
otherwise the table is combined.
Most OO code will set attributes in the __init__
On Sun, Feb 12, 2012 at 1:20 AM, Antoine Pitrou solip...@pitrou.net wrote:
On Fri, 10 Feb 2012 16:06:15 +0200
Eli Bendersky eli...@gmail.com wrote:
Following the intensive and fruitful discussion of the (now rejected)
PEP 408
On Sun, Feb 12, 2012 at 2:45 AM, Isaac Morland ijmor...@uwaterloo.ca wrote:
Could the documentation generator simply insert the boilerplate if and only
if the package has the __provisional__ attribute? I'm not an expert in
Python documentation but isn't it generated from properly-formatted
Le 07/02/2012 23:21, Brett Cannon a écrit :
On Tue, Feb 7, 2012 at 15:28, Dirkjan Ochtman dirk...@ochtman.nl wrote:
Yeah, startup performance getting worse kinda sucks for command-line
apps. And IIRC it's been getting worse over the past few releases...
Anyway, I think there was enough of a
11 matches
Mail list logo
