On 10/3/2011 12:23 PM, Martin v. Löwis wrote:
Am 02.10.2011 17:46, schrieb Benjamin Peterson:
On 10/02/11 01:14, victor.stinner wrote:
PyUnicode_FromKindAndData() raises a ValueError if the kind is unknown
Also, could I remind you that a better commit message is probably
make
On 10/5/2011 1:43 PM, victor.stinner wrote:
http://hg.python.org/cpython/rev/055174308822
changeset: 72699:055174308822
user:Victor Stinnervictor.stin...@haypocalc.com
date:Wed Oct 05 01:31:05 2011 +0200
summary:
Document requierements of Unicode kinds
files:
On 10/5/2011 7:53 PM, Victor Stinner wrote:
Le mercredi 5 octobre 2011 21:25:22, Terry Reedy a écrit :
+ - PyUnicode_1BYTE_KIND (1):
+
+ * character type = Py_UCS1 (8 bits, unsigned)
+ * if ascii is 1, at least one character must be in range
+ U
On 10/5/2011 8:07 PM, Antoine Pitrou wrote:
On Thu, 6 Oct 2011 10:55:07 +1100
Cameron Simpsonc...@zip.com.au wrote:
Equally, why on earth are you running tests as root!?!?!?!?! Madness.
It's as bad as compiling stuff as root etc etc. A bad idea all around,
securitywise.
Especially, I would
On 10/7/2011 10:06 AM, Nick Coghlan wrote:
On Fri, Oct 7, 2011 at 9:21 AM, Martin v. Löwismar...@v.loewis.de wrote:
if (!PyUnicode_READY(foo)) is not better, also because of
PyUnicode_IS_READY(foo).
I prefer PyUnicode_IS_READY(foo) 0 over PyUnicode_IS_READY(foo) == -1.
Ok, so feel
On 10/7/2011 6:18 AM, Glyph wrote:
To sum up what I believe is now the consensus from this thread:
1. Anyone setting up a buildslave should take care to invoke the build
in an environment where an out-of-control buildbot, potentially
executing arbitrarily horrible and/or malicious
On 10/8/2011 12:57 PM, Giampaolo Rodolà wrote:
I have a couple of doubts about this though.
The first one is about licensing.
Other have answered -- follow the license in giving credit, etc.
My second doubt is about morality.
Although this might be useful to those people who are forced to
On 10/10/2011 4:21 PM, Giampaolo Rodolà wrote:
Thanks everybody for your feedback.
I created a gcode project here:
http://code.google.com/p/pycompat/
This project will be easier if the test suite for a particular
function/class/module is up to par. If you find any gaping holes, you
might
On 10/12/2011 10:58 AM, Barry Warsaw wrote:
On Oct 12, 2011, at 10:24 AM, Benjamin Peterson wrote:
2011/10/12 Antoine Pitrousolip...@pitrou.net:
I'd like some advice on what the best path is in cases such as:
A :exc:`socket.error` is raised for errors from the call
to
On 10/15/2011 7:47 AM, Martin v. Löwis wrote:
-- Issue #10517: After fork(), reinitialize the TLS used by the
PyGILState_* - APIs, to avoid a crash with the pthread implementation in
RHEL 5. Patch - by Charles-François Natali.
You should restore this NEWS entry and add a new one to say that
On 10/17/2011 9:16 AM, Michael Foord wrote:
Hey folks,
The title of the Global Module Index for 3.2 documentation is Python
3.1.3 documentation.
http://docs.python.org/py3k/modindex.html
Verified. Clicking [index] in upper right goes to
http://docs.python.org/py3k/genindex.html
3.2.2
On 6/21/2013 7:45 AM, Antoine Pitrou wrote:
Le Fri, 21 Jun 2013 21:39:10 +1000,
Nick Coghlan ncogh...@gmail.com a écrit :
I think it's OK to expose additional platform specific features in the
C version, and have them fail cleanly with the pure Python version
(rather than silently giving the
On 6/27/2013 11:57 AM, Guido van Rossum wrote:
Yes on one line, capitalized, period. No on single sentence.
Complete and correct docstrings are somewhat rare in idlelib.
About half are missing.
Single lines typically omit the period.
Multiple lines often omit the blank line after the first.
I
On 6/27/2013 12:57 PM, Guido van Rossum wrote:
It was never my intention to enforce that everything has a docstring.
Just that if it does, it looks good.
Ok, I won't add them when a function's name actually makes what it does
obvious. But when I have to spend at least a few minutes reading
On 6/26/2013 9:56 PM, Guido van Rossum wrote:
PEP 257 says this on the formatting of multi-line docstrings:
Multi-line docstrings consist of a summary line just like a one-line
docstring, followed by a blank line, followed by a more elaborate
description.
fileinput has docstrings like
On 6/29/2013 11:59 AM, Tamir Friedman wrote:
Hello,
My name is Tamir Friedman, and I suggest to fix a bug in PlaySound in
winsound library. It's doesn't support the SND_MEMORY feature because
its accepts only str and rejects bytes type.
therefore i include the fixed source file:
Thank you for
On 7/4/2013 3:36 PM, Guido van Rossum wrote:
Maybe the mistake is that the others aren't mentioned? Or perhaps
everything before 3.4a1 should be dropped? I forget what kind of policy
we have for this -- is it all changes in this branch or only changes
unique to this branch?
It cannot be
On 7/7/2013 7:35 AM, Larry Hastings wrote:
On 07/07/2013 07:19 AM, Ronald Oussoren wrote:
Not entirely on topic, but close enough: pydoc currently doesn't use
the __signature__ information at all. Adding such support would be
easy enough, see #17053 for an implementation ;-)
True, it
On 7/13/2013 12:10 AM, Eric Snow wrote:
On Feb 27, 2013 4:31 AM, Michael Foord fuzzy...@voidspace.org.uk
+1 PLY is capable and well tried-and-tested. We used it in Resolver
One to implement a pretty large grammar and it is (in my opinion) best
of breed in the Python parser generator world.
On 7/14/2013 7:09 AM, Nick Coghlan wrote:
Slight adjustment to the proposed wording to ensure completely
undocumented modules are also considered private:
=
Private interfaces
Unless explicitly documented otherwise, a leading underscore on any name
indicates that it is an
On 7/15/2013 12:17 AM, Nick Coghlan wrote:
You'd be surprised how many non-core devs react with astonishment
when I suggest that not documenting something isn't enough to avoid
having users consider it a supported public API - they usually get it
after I point out how far you can usually get
On 7/15/2013 6:22 AM, Nick Coghlan wrote:
At the PyCon AU sprints, some of the sprinters worked on a plan Chris
Jerdonek and I came up with months ago to convert test.support from a
module into a subpackage.
This plan arose from some nasty test suite hacks in the lead up to the
release of
On 7/15/2013 11:11 PM, Nick Coghlan wrote:
I'll look into adding some stronger wording at the top making it clear
that while PEP 8 is a useful starting point and a good default if a
project doesn't have a defined style guide of it's own, it is *not*
the be-all-and-end-all for Python style
On 7/15/2013 7:14 PM, Guido van Rossum wrote:
In a discussion about mypy I discovered that the Python 3 version of
the re module's Match object behaves subtly different from the Python
2 version when the target string (i.e. the haystack, not the needle)
is a buffer object.
In Python 2, the type
On 7/16/2013 7:40 AM, Nick Coghlan wrote:
PEP 8 advises developers to use absolute imports rather than explicit
relative imports.
Why? Using absolute imports couple the internal implementation of a
package to its public name - you can't just change the top level
directory name any more, you
On 7/16/2013 9:39 AM, R. David Murray wrote:
On Tue, 16 Jul 2013 23:19:21 +1000, Steven D'Aprano st...@pearwood.info wrote:
For example, pkgutil includes classes with single-underscore methods, which I take as
private. It also has a function simplegeneric, which is undocumented and not
On 7/17/2013 12:15 AM, Stephen J. Turnbull wrote:
Terry Reedy writes:
On 7/15/2013 10:20 PM, Guido van Rossum wrote:
Or is this something deeper, that a group *is* a new object in
principle?
No, I just think of it as returning a string
That is exactly what the doc
On 7/18/2013 9:15 AM, Ezio Melotti wrote:
In 3.x
string means str, bytes means bytes, bytes-like object means
any object that supports the buffer protocol [0] (including bytes).
string and bytes-like object includes all of them.
I don't think we need to introduce new terms.
I agree. We just
On 7/24/2013 5:12 AM, Bohuslav Kabrda wrote:
Hi all, in recent days, there has been a discussion on fedora-devel
(see thread [1]) about moving to Python 3 as a default.
Default-shift is a known natural language phenomenon.
https://en.wikipedia.org/wiki/Retronym
It is inevitably messy in the
On 7/25/2013 2:48 PM, Christian Heimes wrote:
Hello,
this is an update on my work and the current status of Coverity Scan.
Great work.
Maybe you have noticed a checkins made be me that end with the line CID
#. These are checkins that fix an issue that was discovered by the
static code
On 7/25/2013 6:00 PM, Terry Reedy wrote:
Defect Density:0.05
= defects per thousand lines = 20/400
Anything under 1 is good. The release above reports Samba now at .6.
http://www.pcworld.com/article/2038244/linux-code-is-the-benchmark-of-quality-study-concludes.html
reports Linux 3.8
On 7/25/2013 6:56 PM, Christian Heimes wrote:
Am 26.07.2013 00:32, schrieb Terry Reedy:
# Since false positives should stay constant as true positives are
reduced toward 0, false / all should tend toward 1 (100%) if I
understand the ratio correctly.
Which I did not ;-).
About 40
On 7/30/2013 1:31 PM, R. David Murray wrote:
On Sun, 28 Jul 2013 01:09:43 +0200, terry.reedy python-check...@python.org
wrote:
Issue #18441: Make test.support.requires('gui') skip when it should.
(Consolidating this check and various checks in tkinter files and moving them
to test.support
On 8/1/2013 10:34 AM, Alexander Shorin wrote:
Hi Nick,
On Thu, Aug 1, 2013 at 4:44 PM, Nick Coghlan ncogh...@gmail.com wrote:
9. Explicit guideline not to assign lambdas to names (use def, that's
what it's for)
Even for propose to fit chars-per-line limit
def f(x): return 2*x
f = lambda x:
On 8/1/2013 10:48 AM, Alexander Shorin wrote:
I understand this, but I'm a bit confused about fate of lambdas with
such guideline since I see no more reasons to use them with p.9
statement: long lines, code duplicate, no mock and well tests etc. -
all these problems could be solved with
On 8/1/2013 11:03 AM, Alexander Shorin wrote:
...and, if so, why lambda's?(: Without backward compatibility point I
see that they are getting unofficially deprecated and their usage is
dishonoured.
Please stop both the top-posting and the FUD.
--
Terry Jan Reedy
On 8/1/2013 11:35 AM, Alexander Belopolsky wrote:
Here is one use-case where .. = lambda .. cannot be replaced with def ..
op['add'] = lambda x,y: x+y
op['mul'] = lambda x, y: x*y
Yes, you are binding the functions to named slots, not to names, so not
covered by the PEP. Once might still
On 8/6/2013 3:26 PM, Antoine Pitrou wrote:
I would like to point out that we currently fail at handling GSoC
projects and bringing them to completion.
One cruel example is the set of PEP 3121 / PEP 384 refactorings done by
Robin Schreiber:
At least the following 3.4 buildbots have failed today with an error I
do not understand: AMD64 FreeBSD, PPC64, x86Ubuntu, x86 WinServer 2003.
Except for the Windows BB, it was the only failure and hence the only
reason to not be green.
ERROR: test_xmlcharnamereplace
This run recorded here shows a green test (it appears to have timed out)
http://buildbot.python.org/all/builders/x86%20Windows7%203.x/builds/7017
but the corresponding log for this Windows bot
http://buildbot.python.org/all/builders/x86%20Windows7%203.x/builds/7017/steps/test/logs/stdio
has the
On 8/13/2013 5:06 AM, Christian Heimes wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
CVE-2013-4238 has been signed to NULL bytes in subjectAltName issue.
assigned...
http://bugs.python.org/issue18709
http://www.openwall.com/lists/oss-security/2013/08/13/2
Should we assign a
On 8/13/2013 7:51 PM, Steven D'Aprano wrote:
http://bugs.python.org/issue18606
Tests at end of statistics.patch.
and I'm about to submit a patch containing my updated code and tests,
but I've run into a problem with testing. My existing tests use
unittest, and follow the basic boilerplate
On 8/14/2013 12:09 PM, Nick Coghlan wrote:
On 14 August 2013 11:55, Brett Cannon br...@python.org wrote:
I view a deprecation as the same thing. If we leave the module in until
Python 4 then I can live with that, but simply moving documentation around
is not enough to communicate to those who
On 8/14/2013 9:25 PM, Steven D'Aprano wrote:
The tests aren't
yet integrated with the test runner but are runnable manually.
What do you mean? With the changes I gave you, they run fine as part of
the test suite.
--
Terry Jan Reedy
___
Related to the current deprecation discussion:
http://bugs.python.org/issue13248
This is a master list of deprecated items scheduled for removal in 3.4.
Anything that is going to be removed should be done now, before the next
alpha, methinks.
--
Terry Jan Reedy
On 8/15/2013 8:29 AM, R. David Murray wrote:
A number of us (I don't know how many) have clearly been thinking about
Python 4 as the time when we remove cruft. This will not cause any
backward compatibility issues for anyone who has paid heed to the
deprecation warnings, but will for those who
On 8/15/2013 4:16 PM, Eric V. Smith wrote:
itertools.chain.from_iterable. But I think that was a mistake, too. As a
recent discussion showed, it's not exactly discoverable. The fact that
it's not mentioned in the list of functions at the top of the
documentation doesn't help. And chain is
On 8/14/2013 9:25 PM, Steven D'Aprano wrote:
Hi all,
I have raised a tracker item and PEP for adding a statistics module to
the standard library:
http://bugs.python.org/issue18606
http://www.python.org/dev/peps/pep-0450/
There has been considerable discussion on python-ideas,
I have
On 8/15/2013 10:44 PM, Steven D'Aprano wrote:
The most obvious case is datetime: we have datetime(), and
datetime.now(), datetime.today(), and datetime.strftime(). The only API
difference between it and median is that datetime is a type and median
is not, but that's a difference that makes no
On 8/21/2013 4:52 PM, R. David Murray wrote:
On Wed, 21 Aug 2013 14:34:33 -0500, Tim Peters tim.pet...@gmail.com wrote:
[Brett]
...
After reading that sentence I realize there is a key not missing: I see
no reason NOT to help visibly shutter the 3.2. branch IOW I say do the
null merge.
On 8/24/2013 10:03 AM, Nick Coghlan wrote:
I have not used ET or equivalent, but I do have opinions on function names.
Looking at the current documentation of ElementTree sets of alarm
bells on that front, as it contains the following method descriptions
for XMLParser:
close()
On 8/24/2013 8:51 AM, Stefan Behnel wrote:
Antoine Pitrou, 24.08.2013 13:53:
This would also imply extension module have to be subclasses of the
built-in module type. They can't be arbitrary objects like Stefan
proposed. I'm not sure what the latter enables, but it would probably
make things
On 8/25/2013 7:54 AM, Stefan Behnel wrote:
And what if you do from extmodule import some_function in a Python
module? Then reloading couldn't replace that reference, just as for normal
Python modules. Meaning that you'd still have to keep both modules properly
alive in order to prevent crashes
On 8/29/2013 7:24 PM, Sturla Molden wrote:
Do the numbers add up?
.005 defects in 1,000 lines of code is one defect in every 200,000 lines of
code.
However they also claim that to date, the Coverity Scan service has analyzed nearly
400,000 lines of Python code and identified 996 new defects
On 8/30/2013 8:18 AM, Christian Heimes wrote:
By the way Coverity Scan doesn't understand Python code. It can only
analyzes C, C++ and Java code.
Have you (or Coverity) thought about which, if any, of the C defect
categories apply to Python? (Assuming no use of ctypes ;-). Would it
make any
On 8/30/2013 9:37 PM, Ryan Gonzalez wrote:
I still think non-blocking sounds network-related...
But it isn't ;-). Gui apps routinely use event loops and/or threads or
subprocesses to avoid blocking on either user input (which can come from
keyboard or mouse) and maybe disk operations and
Speaking of which, it also doesn't work (well) with subinterpreters:
Could someone briefly explain 'subinterpreter' or point me somewhere in
the docs? It appears throughout this thread but there is no index or
glossary entry.
--
Terry Jan Reedy
On 9/1/2013 5:04 PM, Antoine Pitrou wrote:
On Sun, 1 Sep 2013 23:02:17 +0200 (CEST)
tim.peters python-check...@python.org wrote:
Windows developers: to get the correct line endings in your checkout,
delete Lib\test\xmltestdata, and then hg revert that directory.
Or, in Tortoisehg
On 9/1/2013 5:13 PM, Stefan Behnel wrote:
Antoine Pitrou, 01.09.2013 22:06:
On Sun, 01 Sep 2013 16:02:33 -0400
Terry Reedy wrote:
Speaking of which, it also doesn't work (well) with subinterpreters:
Could someone briefly explain 'subinterpreter' or point me somewhere in
the docs? It appears
On 9/1/2013 6:59 PM, Eli Bendersky wrote:
On Sat, Aug 31, 2013 at 4:52 PM, Terry Reedy tjre...@udel.edu
mailto:tjre...@udel.edu wrote:
On 8/31/2013 6:19 PM, eli.bendersky wrote:
[issue #18730]
Wrong issue number I think
On 9/6/2013 11:55 AM, Andrew Miller wrote:
I've just checked on Python 2.7.5 and Python 3.3.2 (Win32 versions).
In Python 3.3.2 unicodedata.unidata_version is set to '6.1.0'.
In Python 2.7.5 it is set to '5.2.0' so it looks as though this version
is no longer being updated.
In general, new
On 9/8/2013 5:41 PM, Guido van Rossum wrote:
On Sun, Sep 8, 2013 at 1:48 PM, Oscar Benjamin
oscar.j.benja...@gmail.com wrote:
On 8 September 2013 18:32, Guido van Rossum gu...@python.org wrote:
Going over the open issues:
- Parallel arrays or arrays of tuples? I think the API should require
On 9/8/2013 10:57 PM, Stephen J. Turnbull wrote:
I don't necessarily find this persuasive. It's more common when
working with existing databases that you add variables than add
observations.
My experience with general scientific research is the opposite. One
decides on the variables to
On 9/11/2013 10:10 AM, Barry Warsaw wrote:
On Sep 11, 2013, at 01:09 PM, Serhiy Storchaka wrote:
In ideal it should be one high-quality (float64?) multichannel (5+1?) but
short master file and it's lower-quality copies made by third-party tools. In
ideal the content should be related to
On 9/14/2013 1:45 PM, antoine.pitrou wrote:
http://hg.python.org/cpython/rev/4f5815747f58
changeset: 85701:4f5815747f58
user:Antoine Pitrou solip...@pitrou.net
date:Sat Sep 14 19:45:47 2013 +0200
summary:
Issue #18937: Add an assertLogs() context manager to unittest.TestCase
On 9/16/2013 4:14 PM, R. David Murray wrote:
Well, we tend to avoid single boolean arguments in favor of differently
named functions.
The stdlib has lots of boolean arguments. My impression is that they are
to be avoided when they would change the return type or otherwise do
something
On 2.7, license() return a text that includes a complete list of
releases from 1.6 to 2.7 and stops there
Release Derived YearOwner GPL-
fromcompatible? (1)
0.9.0 thru 1.2 1991-1995 CWI
On 9/17/2013 11:48 AM, MRAB wrote:
On 17/09/2013 16:37, Terry Reedy wrote:
On 2.7, license() return a text that includes a complete list of
releases from 1.6 to 2.7 and stops there
Release Derived YearOwner GPL-
from
When an AttributeError is raised in a __del__ method, it is caught and
ignored, except that it is not completely ignored but is replaced by a
warning message sent to stderr. Example:
class C():
def __del__(self): raise AttributeError
c=C()
del c
Exception AttributeError:
On 9/21/2013 6:15 PM, R. David Murray wrote:
On Sat, 21 Sep 2013 17:16:41 -0400, Terry Reedy tjre...@udel.edu wrote:
When an AttributeError is raised in a __del__ method, it is caught and
ignored, except that it is not completely ignored but is replaced by a
warning message sent to stderr
On 9/21/2013 10:30 PM, Guido van Rossum wrote:
Exceptions in __del__ point to bugs (sometimes in the stdlib) that
should be fixed, period. The only reason they do not result in
exceptions that are properly bubbled up and catchable is because __del__
is called from a DECREF macro which has no
On 9/22/2013 10:25 AM, Nick Coghlan wrote:
As Georg noted, we'd have to do some fancy footwork to make sure
autodoc didn't pick up the wrong module versions for the standard
library docs, though.
Is that a one-time nuisance, a per-module nuisance, a per-autodoc-use
nuisance, or a per-build
On 9/22/2013 2:41 PM, Guido van Rossum wrote:
On Sun, Sep 22, 2013 at 10:35 AM, Terry Reedy tjre...@udel.edu
mailto:tjre...@udel.edu wrote:
On 9/21/2013 10:30 PM, Guido van Rossum wrote:
Exceptions in __del__ point to bugs (sometimes in the stdlib) that
should be fixed
On 9/22/2013 10:04 PM, Guido van Rossum wrote:
If I had the final word, I'd recommend using the current docstrings as
the .rst contents and replacing the docstrings with the 1-2 line
function descriptions from the PEP, e.g.:
* median(data) - median (middle value) of data, taking
On 9/23/2013 11:18 AM, Skip Montanaro wrote:
It would be great if the docstring contained a link to the online
documentation.
That would have to be a feature of help(), not hardcoded in each docstring.
That *is* a feature of the help function:
Help on built-in module sys:
help(sys)
NAME
On 9/23/2013 10:56 AM, Guido van Rossum wrote:
I think 60 is just a guideline. In stdlib .py source code I want it not
to extend beyond the 79th column (see recent PEP 8 argument). For a
PEP 8 says Limit all lines to a maximum of 79 characters.
For flowing long blocks of text with fewer
On 9/22/2013 10:44 PM, Guido van Rossum wrote:
Glad you like it. I still do, too, but I've given up hope to convince
all core developers to stick to this style. :-(
[me] ('Return' rather than 'Returns' is the current convention.)
That's actually a religious argument which in the stdlib
On 9/23/2013 12:23 PM, R. David Murray wrote:
On Mon, 23 Sep 2013 17:22:45 +0200, Antoine Pitrou solip...@pitrou.net wrote:
On Mon, 23 Sep 2013 18:51:04 +1000
Nick Coghlan ncogh...@gmail.com wrote:
On 23 September 2013 18:45, Antoine Pitrou solip...@pitrou.net wrote:
Le Mon, 23 Sep 2013
On 9/26/2013 3:17 AM, Nick Coghlan wrote:
On 26 September 2013 16:53, Georg Brandl g.bra...@gmx.net wrote:
Sure, that's doable, but it dumps the full repr of obj in the middle
of the sentence. The thing that's not practical is the neat and tidy
wording Georg proposed, because the thing passed
On 9/27/2013 10:26 AM, Paul Moore wrote:
[snip longish post]
I want to summarize the main points of what I believe Paul said and
strongly agree with them.
* For this issue, and especially for backporting to 2.7/3.3, we should
consider Windows, Mac, and *nix distributions as separate cases.
On 9/27/2013 3:10 PM, Donald Stufft wrote:
On Sep 27, 2013, at 2:50 PM, Terry Reedy tjre...@udel.edu wrote:
I add: for 2.7/3.3, there is consequently no need for _ensurepip to be in /Lib
after installation, even if temporarily added*. If it is not there, there is no
change the the stdlib
On 9/28/2013 7:28 AM, Kevin Ngugi wrote:
Hi, I just downloaded Python 3.3 top teach myself how to program, I am
new to programming, but the guide I am using requires me to access the
toolbar, which I cannot seem to find. How do I find it and have it
displayed on the interface? I tried v 3.1 but
On 9/22/2013 10:44 PM, Guido van Rossum wrote:
On Sun, Sep 22, 2013 at 7:25 PM, Terry Reedy tjre...@udel.edu
('Return' rather than 'Returns' is the current convention.)
That's actually a religious argument which in the stdlib takes no strict
position -- a quick grep shows that both
On 10/8/2013 9:31 PM, Benjamin Peterson wrote:
2013/10/8 Larry Hastings la...@hastings.org:
This PEP proposes a backwards-compatible syntax that should
permit implementing any builtin in pure Python code.
This is rather too strong. You can certainly implement them; you just
have to implement
On 10/9/2013 9:51 AM, Larry Hastings wrote:
Again, I don't expect this syntax to be implemented any time soon. But
this does raise a mild sore point: Maciej and Armin Rigo tell me that
PyPy's implementation of range() looks like this:
def range(x, y=None, step=None):
The None above is not
On 10/9/2013 1:05 PM, Larry Hastings wrote:
First, if you're proposing to change the signature of range()... well,
good luck. Any proposals I made like that got shot down almost
immediately. I /think/ Guido said somewhere range isn't changing.
deal with it., though I admit I don't have a
On 10/10/2013 10:48 AM, nick.coghlan wrote:
http://hg.python.org/peps/rev/405b80d54b7d
changeset: 5188:405b80d54b7d
user:Nick Coghlan ncogh...@gmail.com
date:Fri Oct 11 00:47:47 2013 +1000
summary:
Revise PEP 453 to be docs-only for 2.7 3.3
- all functional changes are now
On 10/11/2013 3:37 AM, Hu, Hao (NSN - CN/Beijing) wrote:
This list is for development *of* Python and CPython. Usage questions
should be directed elsewhere, such as python-list. Idle questions can be
directed to the idle-sig list. Both can be accessed through
news.gmane.org as
On 10/11/2013 8:04 AM, Serhiy Storchaka wrote:
11.10.13 13:33, Eric V. Smith написав(ла):
And Antoine has again taught me a new word:
polysemic: having more than one meaning; having multiple meanings
There is no such word in my dictionaries. :( Only polysemous and
polysemantic.
On 10/16/2013 5:01 PM, Peter Portante wrote:
Hello,
Is there a reason why the stdlib socket module _fileobject.flush()
method is using ._rbufsize instead of ._wbufsize at line 297 (Python
2.7.3), where it determines the buffer_size value to be used for
_sock.sendall()? Does anybody know the
On 10/17/2013 12:06 PM, Barry Warsaw wrote:
On Oct 18, 2013, at 01:26 AM, Nick Coghlan wrote:
By contrast, suppress() and redirect_stdout() are the *first* general
purpose context managers added to contextlib since its incarnation in
Python 2.5 (although there have been many various domain
On 10/17/2013 7:35 PM, Nick Coghlan wrote:
On 18 Oct 2013 06:59, Xavier Morel catch-...@masklinn.net
mailto:catch-...@masklinn.net wrote:
On 2013-10-17, at 22:11 , Ethan Furman wrote:
On 10/17/2013 01:03 PM, Terry Reedy wrote:
class suppress:
def __init__(self, *exceptions
On 10/18/2013 4:10 AM, Paul Moore wrote:
On 17 October 2013 23:40, Larry Hastings la...@hastings.org wrote:
For those interested parties: Guido just checked asyncio, aka Tulip, aka
PEP 3156, in to trunk. I expect it to be part of Python 3.4.0a4,
hopefully to be released this weekend.
Cool!
I know that many core devs subscribe to the new tracker issues list. If
you skipped over
http://bugs.python.org/issue19335
because it was (mis) titled as an Idle issue (as I presume most would),
you might want to reconsider as it is actually a code and in particular,
a codeop issue. Consider
Progess on the Python3 as 'standard Python' front: Yesterday, FESCO
(Fedora Steering Committee?) approved a proposal to make Python 3
(version unspecified, I presume 3.3 or 3.4) the default Python in Fedora
22 (I did not see a date anywhere).
http://lwn.net/Articles/571528/
On 10/25/2013 6:55 PM, Tae Wong wrote:
Here's the codeaccess.txt file.
https://wesnoth-contribcommunity.googlecode.com/svn/codeaccess.txt
This seems to be an old copy of Misc/ACKS except that non-ascii chars
are not displayed correctly as a result of some encoding snafu.
All committer
On 10/31/2013 10:57 AM, Christian Heimes wrote:
I didnt' see this at first:
STACK was run against a number of systems written in C/C++ and
it found 160 new bugs in the systems tested, including ...
and Python (5).
Has anybody contact us? I neither saw a bug report nor a mail to
On 11/4/2013 1:09 AM, Zachary Ware wrote:
On Sun, Nov 3, 2013 at 10:54 PM, Terry Reedy tjre...@udel.edu wrote:
On 11/3/2013 11:48 PM, terry.reedy wrote:
http://hg.python.org/cpython/rev/cced7981ec4d
changeset: 86908:cced7981ec4d
branch: 2.7
user:Terry Jan Reedy tjre...@udel.edu
On 11/4/2013 5:15 PM, Nick Coghlan wrote:
- I actually have --no-commit configured as a standard option for hg
import in my .hgrc file so I never forget
On Windows, hg uses .ini files. Do you have any idea what the
[section]
option = value
would look like? There is gui dialog for managing the
On 11/5/2013 12:50 AM, Georg Brandl wrote:
mercurial.ini setting with tortoisehg workbench
[defaults]
import = --no-commit
Thank you. A message in a patch is now ignored rather than
auto-committed. I still have to click away the edit box that would allow
me to enter a message and override
1201 - 1300 of 2415 matches
Mail list logo
