Hi,
I posted this (by accident) off the list:
On 2012-11-14, at 23:43 , Chris Withers wrote:
On 14/11/2012 22:37, Chris Withers wrote:
On 14/11/2012 10:11, mar...@v.loewis.de wrote:
def xdict(**kwds):
return kwds
Hah, good call, this trumps both of the other options:
100 -r 5 -v
When python is being run from a compile environment, it detects this by looking
for Lib folders in directories above the one containing the executable.
(I always thought that this special execution mode, hardwired in, was a bit
odd, and suggested that this could be made a function of pep405)
Okay, that means I need to re-install svn, cool.
But I should mention that this needs to be mentioned in the core development
FAQs, setting up and so forth.
There is no mention of it there. Perhaps the unix makefiles get the proper
version, but a windows developer has to fetch those externals
mar...@v.loewis.de wrote:
It's faster than calling dict() because the dict code will
create a second dictionary, and discard the keywords dictionary.
Perhaps in the case where dict() is called with keyword
args only, it could just return the passed-in keyword
dictionary instead of creating
On 2012-10-14 02:06 +0800, Xavier Morel wrote:
1. Why didn't you report that on the tracker?
Reported: http://bugs.python.org/issue16476
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
An unexpected error occurred during the processing
of your message. The tracker administrator is being
notified.
Return-Path: python-dev@python.org
X-Original-To: rep...@bugs.python.org
Delivered-To: roundup+trac...@psf.upfronthosting.co.za
Received: from mail.python.org (mail.python.org
Greg Ewing, 15.11.2012 11:48:
mar...@v.loewis.de wrote:
It's faster than calling dict() because the dict code will
create a second dictionary, and discard the keywords dictionary.
Perhaps in the case where dict() is called with keyword
args only, it could just return the passed-in keyword
Stefan Behnel stefan_ml at behnel.de writes:
Right. If that makes a difference, it's another bug.
Stefan
It's fixed, with, I will note, fewer lines of code than many messages in this
thread:
https://bitbucket.org/pypy/pypy/changeset/c30cb1dcb7a9adc32548fd14274e4995
Alex
On 11/15/2012 9:58 AM, Stefan Behnel wrote:
Greg Ewing, 15.11.2012 11:48:
mar...@v.loewis.de wrote:
It's faster than calling dict() because the dict code will
create a second dictionary, and discard the keywords dictionary.
Perhaps in the case where dict() is called with keyword
args only,
On 15/11/2012 4:21pm, Terry Reedy wrote:
I was thinking that CPython could check the ref count of the input
keyword dict to determine whether it is newly created and can be
returned or is pre-existing and must be copied. But it seems not so.
def d(**x): return sys.getrefcount(x)
import sys
An unexpected error occurred during the processing
of your message. The tracker administrator is being
notified.
Return-Path: python-dev@python.org
X-Original-To: rep...@bugs.python.org
Delivered-To: roundup+trac...@psf.upfronthosting.co.za
Received: from mail.python.org (mail.python.org
An unexpected error occurred during the processing
of your message. The tracker administrator is being
notified.
Return-Path: python-dev@python.org
X-Original-To: rep...@bugs.python.org
Delivered-To: roundup+trac...@psf.upfronthosting.co.za
Received: from mail.python.org (mail.python.org
Hi Kristjan,
does that mean that your scheme simply works, without any config step
necessary after I did my checkout?
This would in fact be an interesting alternative to
Python setup.py develop
but I'm not sure if this is the same scheme on windows and Os X.
Getting this part right was
Stefan Behnel wrote:
This should work as long as this still creates a copy of d at some point:
d = {...}
dict(**d)
It will -- the implementation of the function call opcode always
creates a new keyword dict for passing to the called function.
--
Greg
Hi guys,
I am bored of installing things.
Bored of things that happen to not work for some minor reasons.
Reasons that are not immediately obvious.
Things that don't work because some special case was not handled.
Things that compile for half an hour and then complain that something is not as
On Nov 14, 2012, at 5:37 PM, Chris Withers wrote:
On 14/11/2012 10:11, mar...@v.loewis.de wrote:
Zitat von Chris Withers ch...@simplistix.co.uk:
a_dict = dict(
x = 1,
y = 2,
z = 3,
...
)
What can we do to speed up the former case?
It should be possible to
An unexpected error occurred during the processing
of your message. The tracker administrator is being
notified.
Return-Path: python-dev@python.org
X-Original-To: rep...@bugs.python.org
Delivered-To: roundup+trac...@psf.upfronthosting.co.za
Received: from mail.python.org (mail.python.org
Are you familiar with executing directories having __main__.py as python
scripts?
Daniel Holth
On Nov 15, 2012, at 4:43 PM, Christian Tismer tis...@stackless.com wrote:
Hi Kristjan,
does that mean that your scheme simply works, without any config step
necessary after I did my checkout?
Hello, Christian!
On Fri, Nov 16, 2012 at 12:10:09AM +0100, Christian Tismer
tis...@stackless.com wrote:
I am bored of installing things.
Bored of things that happen to not work for some minor reasons.
Reasons that are not immediately obvious.
Things that don't work because some special
19 matches
Mail list logo
