How is this proposal of di"..." more than a different spelling of lambda
i"..."? (I think it's a great idea — but am wondering if there are some
extra semantics that I missed)
I don't think there's any need to preserve the values of the {...} (or
${...}) constituents — the normal closure mechanism
2015-08-16 7:21 GMT-07:00 Paul Moore :
> 2. By far and away the most common use for me would be things like
> print(f"Iteration {n}: Took {end-start) seconds"). At the moment I use
> str,format() for this, and it's annoyingly verbose. This would be a
> big win, and I'm +1 on the PEP for this specif
On Sun, Aug 16, 2015 at 7:08 AM, Guido van Rossum wrote:
> (I'm only familiar with the GitHub PR flow, and I don't like its behavior,
> which seems to always create an extra merge revision for what I consider as
> logically a single commit.)
For whatever it's worth, this is a "feature": the extra
On 08/16/2015 07:08 AM, Guido van Rossum wrote:
I presume the issue here is that Hg is so complicated that everyone
knows a different subset of the commands and semantics.
I personally don't know what the commands for cherry-picking a
revision would be.
There are a couple. The command you'd
On Sun, Aug 9, 2015 at 3:25 PM Brett Cannon wrote:
>
> On Sun, Aug 9, 2015, 13:51 Peter Ludemann via Python-Dev <
> python-dev@python.org> wrote:
>
> Most of my outputs are log messages, so this proposal won't help me
> because (I presume) it does eager evaluation of the format string and the
> l
On Sun, Aug 16, 2015 at 8:55 PM, Eric V. Smith wrote:
> Thanks, Paul. Good feedback.
>
Indeed, I smiled when I saw Paul's post.
> Triple quoted and raw strings work like you'd expect, but you're right:
> the PEP should make this clear.
>
> I might drop the leading spaces, for a technical reaso
Thanks, Paul. Good feedback.
Triple quoted and raw strings work like you'd expect, but you're right: the PEP
should make this clear.
I might drop the leading spaces, for a technical reason having to deal with
passing the strings in to str.format. But I agree it's not a big deal one way
or the
On August 16, 2015 at 11:26:08 AM, Steven D'Aprano (st...@pearwood.info) wrote:
> On Sun, Aug 16, 2015 at 10:52:00AM -0400, Donald Stufft wrote:
>
> > > So what is the benefit of including wheel with ensurepip?
> >
> > pip has an optional dependency on wheel, if you install that optional
> > de
On Sun, 16 Aug 2015 11:24:32 -0400, "R. David Murray"
wrote:
> On Sun, 16 Aug 2015 00:13:10 -0700, Larry Hastings wrote:
> > 3. After your push request is merged, you pull from
> > bitbucket.com/larry/cpython350 into hg.python.org/cpython and merge
> > into 3.5. In this version I don't
The 3.5.0 patch flow question also brings up the question of how we
are managing NEWS for 3.5.0 vs 3.5.1. We have some commits that
are going in to both 3.5.0a2 and 3.5.1, and some that are only going
in to 3.5.1. Currently the 3.5.1 NEWS says things are going in to
3.5.0a2, but that's obviously
On Sun, 16 Aug 2015 00:13:10 -0700, Larry Hastings wrote:
>
>
> So far I've accepted two pull requests into
> bitbucket.com/larry/cpython350 in the 3.5 branch, what will become
> 3.5.0rc2. As usual, it's the contributor's responsibility to merge
> forward; if their checkin goes in to 3.5, it
On Sun, Aug 16, 2015 at 10:52:00AM -0400, Donald Stufft wrote:
> > So what is the benefit of including wheel with ensurepip?
>
> pip has an optional dependency on wheel, if you install that optional
> dependency than you’ll get the implicit wheel cache enabled by default
> which can drastically
On August 16, 2015 at 10:41:42 AM, Steven D'Aprano (st...@pearwood.info) wrote:
> On Sun, Aug 16, 2015 at 02:17:09PM +0100, Paul Moore wrote:
>
> > Sorry I'm late to this, but I would very much like to see wheel
> > installed with ensurepip on at least Windows.
>
> I seem to be missing someth
On Sun, Aug 16, 2015 at 02:17:09PM +0100, Paul Moore wrote:
> Sorry I'm late to this, but I would very much like to see wheel
> installed with ensurepip on at least Windows.
I seem to be missing something critical to this entire discussion.
As I understand it, ensurepip is *only* intended to boo
On 16.08.2015 16:08, Guido van Rossum wrote:
> I presume the issue here is that Hg is so complicated that everyone knows a
> different subset of the commands and semantics.
>
> I personally don't know what the commands for cherry-picking a revision
> would be.
>
> I also don't know exactly what h
On 2015-08-16, at 16:08 , Guido van Rossum wrote:
> I presume the issue here is that Hg is so complicated that everyone knows a
> different subset of the commands and semantics.
>
> I personally don't know what the commands for cherry-picking a revision would
> be.
graft
> I also don't know
On 8 August 2015 at 02:39, Eric V. Smith wrote:
> Following a long discussion on python-ideas, I've posted my draft of
> PEP-498. It describes the "f-string" approach that was the subject of
> the "Briefer string format" thread. I'm open to a better title than
> "Literal String Formatting".
>
> I
I presume the issue here is that Hg is so complicated that everyone knows a
different subset of the commands and semantics.
I personally don't know what the commands for cherry-picking a revision
would be.
I also don't know exactly what happens when you merge a PR using bitbucket.
(I'm only famil
On 8 August 2015 at 04:53, Nick Coghlan wrote:
>> I do however think it would make ensurepip itself better, so I’m not dead
>> set against it, mostly just worried about ramifications.
>
> I'd advise against letting concerns about Linux distro politics hold
> you back from making ensurepip as good
So far I've accepted two pull requests into
bitbucket.com/larry/cpython350 in the 3.5 branch, what will become
3.5.0rc2. As usual, it's the contributor's responsibility to merge
forward; if their checkin goes in to 3.5, it's their responsibility to
also merge it into the hg.python.org/cpyth
20 matches
Mail list logo