On Wed, Aug 12, 2015 at 3:01 AM, R. David Murray rdmur...@bitdance.com wrote:
Sorry, trailing comma outside () was a shorthand for 'trailing comma
on a complete statement'. That is, what trips me up is going from
something like:
dict(abc=1,
foo=2,
bar=3,
)
ISAAC J SCHWABACHER schrieb am 11.08.2015 um 01:05:
I don't know about you, but I sure like this better than what you have:
code.putlines(f
static char {entry.doc_cname}[] = {
split_string_literal(escape_bytestring(docstr))};
{ # nested!
f
#if CYTHON_COMPILING_IN_CPYTHON
struct
Cameron Simpson wrote:
To illustrate, there's a consumer rights TV snow here with a segment
called F.U. Tube, where members of the public describe ripoffs and
other product failures in video form. While a phonetic play on the name
YouTube, the abbreviation also colloquially means just what you
Barry Warsaw writes:
Besides, any expression you have to calculate can go in a local
that will get interpolated.
Sure, but that style should be an application programmer choice.
If this syntax can't replace the vast majority of cases where the
format method is invoked on a literal string
So, there's a patch on issue 9232 - allow trailing commas in function
definitions - but there's been enough debate that I suspect we need a
PEP.
Would love it if someone could correct me, but I'd like to be able to
either categorically say 'no' and close the ticket, or 'yes and this
is what
On 11Aug2015 18:07, Greg Ewing greg.ew...@canterbury.ac.nz wrote:
Cameron Simpson wrote:
To illustrate, there's a consumer rights TV snow here with a segment
called F.U. Tube, where members of the public describe ripoffs and
other product failures in video form. While a phonetic play on the
On Tue, Aug 11, 2015 at 09:51:56PM +1000, Chris Angelico wrote:
On Tue, Aug 11, 2015 at 5:08 PM, Cameron Simpson c...@zip.com.au wrote:
On 11Aug2015 18:07, Greg Ewing greg.ew...@canterbury.ac.nz wrote:
Cameron Simpson wrote:
To illustrate, there's a consumer rights TV snow here with a
On Tue, Aug 11, 2015 at 5:08 PM, Cameron Simpson c...@zip.com.au wrote:
On 11Aug2015 18:07, Greg Ewing greg.ew...@canterbury.ac.nz wrote:
Cameron Simpson wrote:
To illustrate, there's a consumer rights TV snow here with a segment
called F.U. Tube, where members of the public describe ripoffs
On Tue, 11 Aug 2015 18:09:34 +1200, Robert Collins robe...@robertcollins.net
wrote:
So, there's a patch on issue 9232 - allow trailing commas in function
definitions - but there's been enough debate that I suspect we need a
PEP.
Would love it if someone could correct me, but I'd like to be
On Wed, Aug 12, 2015 at 12:46 AM, R. David Murray rdmur...@bitdance.com wrote:
(If you wanted to fix an 'oops' trailing comma syntax issue, I'd vote for
disallowing trailing commas outside of (). The number of times I've
ended up with an unintentional tuple after converting a dictionary to a
On 08/10/2015 07:23 PM, Victor Stinner wrote:
Le mardi 11 août 2015, Eric V. Smith e...@trueblade.com
mailto:e...@trueblade.com a écrit :
Oops, I was thinking of going the other way (str.format - f''). Yes, I
think you're correct.
Ah ok.
But in any event, I don't see
On 08/10/2015 04:12 PM, Mike Miller wrote:
Here are my notes on PEP 498.
1. Title: Literal String Formatting
- String Literal Formatting
- Format String Expressions
?
I like String Literal Formatting, but let me sleep on it.
2. Let's call them format strings not f-strings.
This may seam like a simplistic solution to i18n, but why not just add a
method to string objects (assuming we implement f-strings) that just
returns the original, unprocessed string. If the string was not an
f-string, it just returns self. The gettext module can be modified, I
think
On 08/11/2015 11:09 AM, Alexander Walters wrote:
This may seam like a simplistic solution to i18n, but why not just add a
method to string objects (assuming we implement f-strings) that just
returns the original, unprocessed string. If the string was not an
f-string, it just returns self.
On Aug 10, 2015, at 11:05 PM, ISAAC J SCHWABACHER wrote:
code.putlines(f
static char {entry.doc_cname}[] = {
split_string_literal(escape_bytestring(docstr))};
{ # nested!
f
#if CYTHON_COMPILING_IN_CPYTHON
struct wrapperbase {entry.wrapperbase_cname};
#endif
if entry.is_special else ''}
I don't think it needs a PEP. See my response in the issue.
On Tue, Aug 11, 2015 at 8:09 AM, Robert Collins robe...@robertcollins.net
wrote:
So, there's a patch on issue 9232 - allow trailing commas in function
definitions - but there's been enough debate that I suspect we need a
PEP.
On Aug 11, 2015 10:10 AM, Alexander Walters tritium-l...@sdamon.com
wrote:
This may seam like a simplistic solution to i18n, but why not just add a
method to string objects (assuming we implement f-strings) that just
returns the original, unprocessed string. If the string was not an
f-string,
Now with syntax highlighting, if my email client cooperates:
code.putlines(f
static char {entry.doc_cname}[] = {
split_string_literal(escape_bytestring(docstr))};
{ # nested!
f
#if CYTHON_COMPILING_IN_CPYTHON
struct wrapperbase {entry.wrapperbase_cname};
#endif
if entry.is_special else
On 8/11/2015 11:16, Eric V. Smith wrote:
On 08/11/2015 11:09 AM, Alexander Walters wrote:
This may seam like a simplistic solution to i18n, but why not just add a
method to string objects (assuming we implement f-strings) that just
returns the original, unprocessed string. If the string was
there's been enough debate that I suspect we need a
PEP.
I think we might just need another round of discussion here.
Please no :-)
Looking back at the previous discussion, it looked like it's all been
said, and there was almost unanimous approval (with some key mild
disapproval) for the
On Aug 11, 2015 10:19 AM, Wes Turner wes.tur...@gmail.com wrote:
On Aug 11, 2015 10:10 AM, Alexander Walters tritium-l...@sdamon.com
wrote:
This may seam like a simplistic solution to i18n, but why not just add
a method to string objects (assuming we implement f-strings) that just
returns
As a user who has banged my head against this more than once, its not a
feature, its a bug, it does not need a pep (Guido said as much), just
fix it.
On 8/11/2015 11:31, Chris Barker - NOAA Federal wrote:
there's been enough debate that I suspect we need a
PEP.
I think we might just need
On 8/11/2015 11:28, Wes Turner wrote:
On Aug 11, 2015 10:19 AM, Wes Turner wes.tur...@gmail.com
mailto:wes.tur...@gmail.com wrote:
- [ ] review all string interpolation (for injection)
* [ ] review every '%'
* [ ] review every .format()
* [ ] review every f-string (AND LOCALS AND
On Wed, 12 Aug 2015 01:03:38 +1000, Chris Angelico ros...@gmail.com wrote:
On Wed, Aug 12, 2015 at 12:46 AM, R. David Murray rdmur...@bitdance.com
wrote:
(If you wanted to fix an 'oops' trailing comma syntax issue, I'd vote for
disallowing trailing commas outside of (). The number of times
On 08/11/2015 01:25 PM, Sven R. Kunze wrote:
Couldn't you just store the original format string at some
__format_str__ attribute at the formatted string? Just in case you need it.
x = f'{a}'
=
x = '{}'.format(a) # or whatever it turns out to be
x.__format_str__ = '{a}'
Yes. But I
On 08/11/2015 06:47 AM, Eric V. Smith wrote:
2. Let's call them format strings not f-strings.
The latter sounds slightly obnoxious, and also inconsistent with the
others:
r'' raw string
u'' unicode object (string)
f'' format string
On Tue, 11 Aug 2015 08:31:57 -0700, Chris Barker - NOAA Federal
chris.bar...@noaa.gov wrote:
Looking back at the previous discussion, it looked like it's all been
said, and there was almost unanimous approval (with some key mild
disapproval) for the idea, so what we need now is a
Couldn't you just store the original format string at some
__format_str__ attribute at the formatted string? Just in case you need it.
x = f'{a}'
=
x = '{}'.format(a) # or whatever it turns out to be
x.__format_str__ = '{a}'
On 11.08.2015 17:16, Eric V. Smith wrote:
On 08/11/2015 11:09 AM,
On Tue, Aug 11, 2015 at 10:52 AM, Alexander Walters tritium-l...@sdamon.com
wrote:
On 8/11/2015 11:28, Wes Turner wrote:
On Aug 11, 2015 10:19 AM, Wes Turner wes.tur...@gmail.com wrote:
- [ ] review all string interpolation (for injection)
* [ ] review every '%'
* [ ] review every
I don't know about you, but I sure like this better than what you have:
code.putlines(f
static char {entry.doc_cname}[] = {
split_string_literal(escape_bytestring(docstr))};
{ # nested!
f
#if CYTHON_COMPILING_IN_CPYTHON
struct wrapperbase {entry.wrapperbase_cname};
#endif
if
We saw and fixed it before RC 1. I'll check whether that fix didn't stick, but
go ahead, open an issue and assign me.
Cheers,
Steve
Top-posted from my Windows Phone
From: MRABmailto:pyt...@mrabarnett.plus.com
Sent: 8/11/2015 17:25
To:
On 2015-08-12 02:05, Steve Dower wrote:
We saw and fixed it before RC 1. I'll check whether that fix didn't
stick, but go ahead, open an issue and assign me.
It's issue 24847.
From: MRAB
As the subject says, I'm unable to import tkinter in Python 3.5.0rc1.
The console says:
C:\Python35python
Python 3.5.0rc1 (v3.5.0rc1:1a58b1227501, Aug 10 2015, 05:18:45) [MSC
v.1900 64 bit (AMD64)] on win32
Type help, copyright, credits or license for more information.
import tkinter
Stefan Behnel wrote:
Syntax highlighting and in-string expression completion should eventually
help, once IDEs support it.
Concerning that, this is going to place quite a
burden on syntax highlighters. Doing it properly
will require the ability to parse arbitrary Python
expressions, or at
On 08/11/2015 02:56 AM, Larry Hastings wrote:
On 08/10/2015 05:55 PM, Larry Hastings wrote:
I yanked the tarballs off the release page as soon as I suspected something.
I'm rebuilding the tarballs and the docs now. If you grabbed the tarball as
soon as it appeared, it's slightly out of date,
35 matches
Mail list logo
