On Fri, Mar 30, 2012 at 2:12 PM, wrote:
>
> Zitat von Nick Coghlan :
>
>
>> On Fri, Mar 30, 2012 at 2:01 AM, andrew.svetlov
>> wrote:
>>>
>>> +- Issue #14409: IDLE doesn't not execute commands from shell,
>>> + error with default keybinding for Return. (Patch by Roger Serwy)
>>
>>
>> The double
On Thu, Mar 29, 2012 at 22:48, wrote:
> Now that we do have the PEP, I think that should be done properly.
> I thought you offered to rewrite it.
There are definitely areas that I would like to work on, especially
pulling implementation details out and replacing with, as you say,
end-user prose.
Zitat von Brian Curtin :
After talking with Martin and several others during the language
summit and elsewhere around PyCon, PEP 397 should be accepted. I don't
remember who, but some suggested it should just be a regular old
feature instead of going through the PEP process. So...does this even
On Fri, Mar 30, 2012 at 2:01 AM, andrew.svetlov
wrote:
> +- Issue #14409: IDLE doesn't not execute commands from shell,
> + error with default keybinding for Return. (Patch by Roger Serwy)
The double negative here makes this impossible to understand. Could we
please get an updated NEWS entry tha
On Fri, Mar 30, 2012 at 12:07 PM, Éric Araujo wrote:
> Le 29/03/2012 22:04, Nick Coghlan a écrit :
>> On Fri, Mar 30, 2012 at 4:26 AM, Carl Meyer wrote:
>>> I've added this option as a comment on bug 1. The title of that bug
>>> is worded such that it could be reasonably resolved either with
Le 29/03/2012 22:04, Nick Coghlan a écrit :
> On Fri, Mar 30, 2012 at 4:26 AM, Carl Meyer wrote:
>> I've added this option as a comment on bug 1. The title of that bug
>> is worded such that it could be reasonably resolved either with the
>> backwards-compatibility fix or the release notes add
On Fri, Mar 30, 2012 at 4:26 AM, Carl Meyer wrote:
> I've added this option as a comment on bug 1. The title of that bug
> is worded such that it could be reasonably resolved either with the
> backwards-compatibility fix or the release notes addition, the release
> managers can decide what see
On Fri, Mar 30, 2012 at 7:50 AM, Brian Curtin wrote:
> On Thu, Mar 29, 2012 at 17:45, Benjamin Peterson wrote:
>> 2012/3/29 Brian Curtin :
>>> After talking with Martin and several others during the language
>>> summit and elsewhere around PyCon, PEP 397 should be accepted. I don't
>>> remember w
Brian Curtin python.org> writes:
> Vinay - is the code you have on bitbucket ready to roll into CPython,
> thus into the installer?
I believe the main C launcher code is ready to roll into CPython. However, the
standalone installer I provide uses WiX rather than msilib, and includes
additional e
2012/3/29 Brian Curtin :
> On Thu, Mar 29, 2012 at 17:45, Benjamin Peterson wrote:
>> 2012/3/29 Brian Curtin :
>>> After talking with Martin and several others during the language
>>> summit and elsewhere around PyCon, PEP 397 should be accepted. I don't
>>> remember who, but some suggested it sho
On Thu, Mar 29, 2012 at 18:08, Glenn Linderman wrote:
> All it needs is official acceptance now, and integration into the release,
> no?
If it wasn't clear, this is what I said in the first post.
___
Python-Dev mailing list
Python-Dev@python.org
http://
On 3/29/2012 3:50 PM, Brian Curtin wrote:
On Thu, Mar 29, 2012 at 17:45, Benjamin Peterson wrote:
> 2012/3/29 Brian Curtin:
>> After talking with Martin and several others during the language
>> summit and elsewhere around PyCon, PEP 397 should be accepted. I don't
>> remember who, but som
On Thu, Mar 29, 2012 at 17:45, Benjamin Peterson wrote:
> 2012/3/29 Brian Curtin :
>> After talking with Martin and several others during the language
>> summit and elsewhere around PyCon, PEP 397 should be accepted. I don't
>> remember who, but some suggested it should just be a regular old
>> fe
2012/3/29 Brian Curtin :
> After talking with Martin and several others during the language
> summit and elsewhere around PyCon, PEP 397 should be accepted. I don't
> remember who, but some suggested it should just be a regular old
> feature instead of going through the PEP process. So...does this
After talking with Martin and several others during the language
summit and elsewhere around PyCon, PEP 397 should be accepted. I don't
remember who, but some suggested it should just be a regular old
feature instead of going through the PEP process. So...does this even
need to continue the PEP pro
On Thu, 29 Mar 2012 23:00:20 +0200, Stefan Behnel wrote:
> R. David Murray, 29.03.2012 22:31:
> > On Thu, 29 Mar 2012 13:09:17 -0700, Guido van Rossum wrote:
> >> On Thu, Mar 29, 2012 at 12:58 PM, R. David Murray wrote:
> >>> Some of us have expressed uneasiness about the consequences of dict
> >>
On 29/03/2012 21:35, Tim Lesher wrote:
From a theoretical standpoint, I can't quite decide what the real error is:
1) the fact that PyGILState_Release() destroys a temporary thread
state that may still be referenced by some objects, or
2) the fact that some code is trying to keep frame objects
On 03/29/2012 04:48 PM, R. David Murray wrote:
On Thu, 29 Mar 2012 16:31:03 -0400, "R. David Murray"
wrote:
On Thu, 29 Mar 2012 13:09:17 -0700, Guido van Rossum wrote:
My original assessment was that this only affects dicts whose keys
have a user-implemented __hash__ or __eq__ implementation
R. David Murray, 29.03.2012 22:31:
> On Thu, 29 Mar 2012 13:09:17 -0700, Guido van Rossum wrote:
>> On Thu, Mar 29, 2012 at 12:58 PM, R. David Murray wrote:
>>> Some of us have expressed uneasiness about the consequences of dict
>>> raising an error on lookup if the dict has been modified, the fix
On Thu, 29 Mar 2012 16:31:03 -0400, "R. David Murray"
wrote:
> On Thu, 29 Mar 2012 13:09:17 -0700, Guido van Rossum wrote:
> > My original assessment was that this only affects dicts whose keys
> > have a user-implemented __hash__ or __eq__ implementation, and that
> > the number of apps that us
On Thu, 29 Mar 2012 13:09:17 -0700, Guido van Rossum wrote:
> On Thu, Mar 29, 2012 at 12:58 PM, R. David Murray
> wrote:
> > Some of us have expressed uneasiness about the consequences of dict
> > raising an error on lookup if the dict has been modified, the fix Victor
> > made to solve one of t
On Thu, Mar 29, 2012 at 12:58 PM, R. David Murray wrote:
> Some of us have expressed uneasiness about the consequences of dict
> raising an error on lookup if the dict has been modified, the fix Victor
> made to solve one of the crashers.
>
> I don't know if I speak for the others, but (assuming t
On Thu, 29 Mar 2012 21:14:32 +0200, =?ISO-8859-15?Q?=22Martin_v=2E_L=F6wis=22?=
wrote:
> Am 29.03.2012 18:21, schrieb Ross Lagerwall:
> > On 03/29/2012 05:07 AM, "Martin v. Löwis" wrote:
> I noticed that text search wasn't working right on the bug tracker, and
> Martin
> has take
Some of us have expressed uneasiness about the consequences of dict
raising an error on lookup if the dict has been modified, the fix Victor
made to solve one of the crashers.
I don't know if I speak for the others, but (assuming that I understand
the change correctly) my concern is that there is
On Wed, Mar 28, 2012 at 06:45, Victor Stinner wrote:
> We have a crash in our product when tracing is enabled by
> sys.settrace() and threading.settrace(). If a Python generator is
> created in a C thread, calling the generator later in another thread
> may crash if Python tracing is enabled.
>
>
Am 29.03.2012 18:21, schrieb Ross Lagerwall:
> On 03/29/2012 05:07 AM, "Martin v. Löwis" wrote:
I noticed that text search wasn't working right on the bug tracker, and
Martin
has taken it offline again to re-index.
>>>
>>> which will, unfortunately, take a few more hours to complete
On 03/29/2012 11:39 AM, David Malcolm wrote:
>> jaraco@vdm-dev:~$ env/bin/python -c "import os; os.urandom()"
>> Traceback (most recent call last):
>> File "", line 1, in
>> AttributeError: 'module' object has no attribute 'urandom'
>
> It looks like this a symptom of the move of urandom to os.
On 03/29/2012 06:39 PM, R. David Murray wrote:
> I get three for 'all' issues, which is certainly wrong. All of them
> have subprocess in the title.
>
> I suspect the search is only searching the title field, which is wrong.
No, #14357 contains 'virtualenv' in the title but it doesn't come up in
On Wed, 2012-03-28 at 18:22 +, Jason R. Coombs wrote:
> I see this was reported as a debian bug.
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665776
>
> To reproduce, using virtualenv 1.7+ on Python 2.7.2 on Ubuntu, create
> a virtualenv. Move that virtualenv to a host with Python 2.7.3R
Thanks Jason for raising this. I just assumed that this was virtualenv's
fault (which it is) and didn't consider raising it here, but a note in
the release notes for the affected Python versions will certainly reach
many more of the likely-to-be-affected users.
FTR, I confirmed that the issue also
On Thu, 29 Mar 2012 18:21:34 +0200, Ross Lagerwall
wrote:
> On 03/29/2012 05:07 AM, "Martin v. Löwis" wrote:
> >>> I noticed that text search wasn't working right on the bug tracker, and
> >>> Martin
> >>> has taken it offline again to re-index.
> >>
> >> which will, unfortunately, take a few m
On 03/29/2012 05:07 AM, "Martin v. Löwis" wrote:
>>> I noticed that text search wasn't working right on the bug tracker, and
>>> Martin
>>> has taken it offline again to re-index.
>>
>> which will, unfortunately, take a few more hours to complete.
>
> It seems to work now, so I turned it on again
If you could, Jordan, please file a bug at bugs.python.org so the
discussion can happen there and be tracked better.
On Wed, Mar 28, 2012 at 03:06, Jordan Schneider wrote:
> Hi python-dev,
>
> Sorry if this is the wrong place to discuss this potential bug - feel free
> to point me in the right d
On Thu, 29 Mar 2012 11:41:46 -, "Jason R. Coombs" wrote:
> Does the issue only exist for Python 2.6 and 2.7?
It might exist for 3.1 and 3.2 as well.
> I'm not familiar with the release process. What's the next step?
I would suggest opening an issue on the tracker and marking it as a
release
On Wed, Mar 28, 2012 at 23:40, Victor Stinner wrote:
>> Does this primarily give a high resolution clock, or primarily a
>> monotonic clock? That's not clear from either the name, or the PEP.
>
> I expect a better resolution from time.monotonic() than time.time().
Sure. And for me that means that
Carl,
I've drafted some notes: http://piratepad.net/PAZ3CEq9CZ
Please feel free to edit them. If you want to chat, I can often be reached
on freenode as 'jaraco' or XMPP at my e-mail address if you want to sprint
on this in real-time.
Does the issue only exist for Python 2.6 and 2.7?
I'm not fa
Hi python-dev,
Sorry if this is the wrong place to discuss this potential bug - feel free to
point me in the right direction if so.
I'm running OS X 10.7.3, and have two python2.7s installed, one system default
in /usr/bin and the other by homebrew symlinked in /usr/local/bin.
While running a
On Wed, Mar 28, 2012 at 19:47, "Martin v. Löwis" wrote:
> Am 27.03.2012 23:11, schrieb "Martin v. Löwis":
>> Upfront hosting (Izak Burger) is going to do a Debian upgrade of the bug
>> tracker machine "soon" (likely tomorrow). This may cause some outage,
>> since there is a lot of custom stuff on
38 matches
Mail list logo
