On Tue, 27 Jan 2015 00:07:08 +0100, Antoine Pitrou wrote:
> On Mon, 26 Jan 2015 16:28:24 -0500
> "R. David Murray" wrote:
> >
> > My use case is a configuration method that takes keyword parameters.
> > In tests I want to specify a bunch of default values for the
> > configuration, but I want in
On 2015-01-26 19:39, Petr Viktorin wrote:
On Mon, Jan 26, 2015 at 8:29 PM, Ethan Furman wrote:
On 01/26/2015 11:24 AM, Barry Warsaw wrote:
On Jan 26, 2015, at 10:55 AM, Ethan Furman wrote:
In the your example
from_env = {'a': 12}
from_config = {'a': 13}
f(**from_env, **from_config)
I w
On Mon, 26 Jan 2015 16:28:24 -0500
"R. David Murray" wrote:
>
> My use case is a configuration method that takes keyword parameters.
> In tests I want to specify a bunch of default values for the
> configuration, but I want individual test methods to be able
> to override those values. So I have
On Mon, 26 Jan 2015 22:05:44 +0100, Antoine Pitrou wrote:
> On Mon, 26 Jan 2015 12:22:20 -0800
> Ethan Furman wrote:
> > On 01/26/2015 12:09 PM, Antoine Pitrou wrote:
> > > On Mon, 26 Jan 2015 12:06:26 -0800
> > > Ethan Furman wrote:
> > >> It destroy's the chaining value and pretty much makes t
On Mon, 26 Jan 2015 12:22:20 -0800
Ethan Furman wrote:
> On 01/26/2015 12:09 PM, Antoine Pitrou wrote:
> > On Mon, 26 Jan 2015 12:06:26 -0800
> > Ethan Furman wrote:
> >> It destroy's the chaining value and pretty much makes the improvement not
> >> an improvement. If there's a possibility that
On 26.01.15 00:59, Guido van Rossum wrote:
Interestingly, the non-dict versions can all be written today using a
double-nested comprehension, e.g. {**x for x in it} can be written as:
{x for x in xs for xs in it}
{x for xs in it for x in xs}
But it's not so straightforward for dict
On 25.01.15 17:08, Antoine Pitrou wrote:
On Sat, 24 Jan 2015 21:10:51 -0500
Neil Girdhar wrote:
To finish PEP 448, I need to update the grammar for syntax such as
{**x for x in it}
Is this seriously allowed by the PEP? What does it mean exactly?
I would understand this as
{k: v for x in
On 01/26/2015 07:25 PM, Skip Montanaro wrote:
> On Mon, Jan 26, 2015 at 12:12 PM, Antoine Pitrou wrote:
>> I also think the multiple-starargs function calls are completely
>> overboard:
>>
>> f(**someargs, **someotherargs)
>>
>> (I might add I've never felt any need for those)
>
> This makes se
On 01/26/2015 09:25 PM, Ethan Furman wrote:
> Do we have our own mailing list for Roundup?
>
> I'm trying to fix the Activity Date search bug (only returns issues where the
> *last* activity was on a date, not *any* activity on a date).
That would be tracker-discuss.
Georg
_
On Mon, Jan 26, 2015 at 12:49 PM, Cyd Haselton wrote:
> Hello,
> I've finally managed to build a (somewhat) working Python port for the
> Android tablet I'm using. Unfortunately, as I quickly found out,
> Python's built-in help function requires tkinter, which requires
> tcl/tk.
What version of
On Mon, Jan 26, 2015 at 10:25 PM, Ethan Furman wrote:
> Do we have our own mailing list for Roundup?
Hi,
Yes: https://mail.python.org/mailman/listinfo/tracker-discuss There is
also a tracker for bugs.p.o:
http://psf.upfronthosting.co.za/roundup/meta/
--Berker
___
On Mon, Jan 26, 2015 at 12:49 PM, Cyd Haselton wrote:
> Unfortunately, as I quickly found out,
> Python's built-in help function requires tkinter, which requires
> tcl/tk.
I'm a little confused. Are you using some sort of freeze system which
is deciding Tkinter is required? I use help() all the t
Do we have our own mailing list for Roundup?
I'm trying to fix the Activity Date search bug (only returns issues where the
*last* activity was on a date, not *any*
activity on a date).
--
~Ethan~
signature.asc
Description: OpenPGP digital signature
On 01/26/2015 12:09 PM, Antoine Pitrou wrote:
> On Mon, 26 Jan 2015 12:06:26 -0800
> Ethan Furman wrote:
>> It destroy's the chaining value and pretty much makes the improvement not an
>> improvement. If there's a possibility that
>> the same key could be in more than one of the dictionaries the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/26/2015 09:43 AM, Barry Warsaw wrote:
> This is head-scratcher code that I'm sure I'd get asked about from
> folks who aren't steeped in all the dark corners of Python. I don't
> know if that's an argument not to adopt the PEP, but it I think i
Looking at pydoc.py, it looks like the Tk is purely optional...and isn't
called from the interpreter. (I'm not a core dev, though, so take that with
a grain of salt.) However, can't you just strip out the gui function and
the one place in the file where it's called?
Again, not a main Python develo
On Mon, 26 Jan 2015 12:06:26 -0800
Ethan Furman wrote:
> It destroy's the chaining value and pretty much makes the improvement not an
> improvement. If there's a possibility that
> the same key could be in more than one of the dictionaries then you still
> have to do the
>
> dict.update(anot
On 01/26/2015 11:39 AM, Petr Viktorin wrote:
> On Mon, Jan 26, 2015 at 8:29 PM, Ethan Furman wrote:
>> On 01/26/2015 11:24 AM, Barry Warsaw wrote:
>>> On Jan 26, 2015, at 10:55 AM, Ethan Furman wrote:
>>>
In the your example
from_env = {'a': 12}
from_config = {'a': 13}
>
On Mon, Jan 26, 2015 at 8:29 PM, Ethan Furman wrote:
> On 01/26/2015 11:24 AM, Barry Warsaw wrote:
>> On Jan 26, 2015, at 10:55 AM, Ethan Furman wrote:
>>
>>> In the your example
>>>
>>> from_env = {'a': 12}
>>> from_config = {'a': 13}
>>>
>>> f(**from_env, **from_config)
>>>
>>> I would think
Hello,
I've finally managed to build a (somewhat) working Python port for the
Android tablet I'm using. Unfortunately, as I quickly found out,
Python's built-in help function requires tkinter, which requires
tcl/tk.
I did download the sources for tcl/tk and built tcl, but found out
that tk requir
On 2015-01-24 7:17 AM, Donald Stufft wrote:
> It’s not just power users that it’s good for, it makes it harder for
> even beginners to use things like backports of modules.
What about cases where new module versions are put in as dependencies of
other packages and they stomp standard library packa
On 01/26/2015 11:24 AM, Barry Warsaw wrote:
> On Jan 26, 2015, at 10:55 AM, Ethan Furman wrote:
>
>> In the your example
>>
>> from_env = {'a': 12}
>> from_config = {'a': 13}
>>
>> f(**from_env, **from_config)
>>
>> I would think 'a' should be 13, as from_config is processed /after/ from_env.
>
On Jan 26, 2015, at 10:55 AM, Ethan Furman wrote:
>In the your example
>
> from_env = {'a': 12}
> from_config = {'a': 13}
>
> f(**from_env, **from_config)
>
>I would think 'a' should be 13, as from_config is processed /after/ from_env.
>
>So which is it?
In the face of ambiguity, refuse the te
On 01/26/2015 10:55 AM, Ethan Furman wrote:
> On 01/26/2015 10:40 AM, Paul Moore wrote:
>
>> There *are* some nastily non-intuitive corner cases (for example, if
>> from_env={'a':12} and from_config={'a':13}, I don't have any sort of
>> intuition as to what a would be in f(**from_env, **from_confi
On Mon, Jan 26, 2015 at 12:55 PM, Ethan Furman wrote:
> So which is it?
Precisely...
S
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-de
On 01/26/2015 10:40 AM, Paul Moore wrote:
> There *are* some nastily non-intuitive corner cases (for example, if
> from_env={'a':12} and from_config={'a':13}, I don't have any sort of
> intuition as to what a would be in f(**from_env, **from_config). I'd
> go with 12 because the PEP links multiple
Of course. I hadn't had time to answer your private e-mail but will do
so soon :-)
Regards
Antoine.
On Mon, 26 Jan 2015 17:24:31 +
"Gregory P. Smith" wrote:
> I want this buildbot to run "make profile-opt" instead of "make all" and
> it'd be best if it could _not_ have --with-pydebug on t
On 26 January 2015 at 18:12, Antoine Pitrou wrote:
> I have to agree with Barry. While the following is obvious even without
> having ever used it:
>
> a, b, *c = range(5)
>
> the following makes me scratch my head and I can't seem to guess what
> the *intent* is - which is very problematic when
On Mon, Jan 26, 2015 at 12:12 PM, Antoine Pitrou wrote:
> I also think the multiple-starargs function calls are completely
> overboard:
>
> f(**someargs, **someotherargs)
>
> (I might add I've never felt any need for those)
This makes sense to me, but I wonder how you resolve the case of
overla
On Mon, 26 Jan 2015 10:46:02 -0500
"R. David Murray" wrote:
> On Mon, 26 Jan 2015 09:43:26 -0500, Barry Warsaw wrote:
> > On Jan 25, 2015, at 09:31 PM, R. David Murray wrote:
> >
> > >> > > {*x for x in it}
> > >> > >
> > >> > > which is a set comprehension, while the other is a dict
> > >> >
I want this buildbot to run "make profile-opt" instead of "make all" and
it'd be best if it could _not_ have --with-pydebug on the ./configure
command line.
I've got a small VM at the moment with one CPU and 600mb ram so just give
it a make -j2 at most to start with.
If that is possible, please a
On Mon, 26 Jan 2015 09:43:26 -0500, Barry Warsaw wrote:
> On Jan 25, 2015, at 09:31 PM, R. David Murray wrote:
>
> >> > > {*x for x in it}
> >> > >
> >> > > which is a set comprehension, while the other is a dict comprehension
> >> > > :)
> >> > >
> >> >
> >> > That distinction doesn't bother m
On Jan 25, 2015, at 09:31 PM, R. David Murray wrote:
>> > > {*x for x in it}
>> > >
>> > > which is a set comprehension, while the other is a dict comprehension :)
>> > >
>> >
>> > That distinction doesn't bother me -- you might as well claim it's
>> > confusing that f(*x) passes positional args
33 matches
Mail list logo
