Good morning,
I read about a "time machine" debugger a long time ago. The debugger
would collect all the information of all the calls and the programmer
can just execute the code without breakpoints. Later, the programmer can
follow the evolution of a variable until it reaches an erroneous val
On 26/09/18 18:23, Michael Selik wrote:
Guido has repeatedly (haha) rejected this proposal [0]. He has written
that he considered it, but decided that in practical code one almost
always loops over data, and does not want an arbitrary number of
iterations. The range object solves this problem.
I don’t think its unreasonable to point out that it’s a *mailing list*. A
firehose of email is generally a sign of good health of a mailing list. Even
so, there are mitigations to the firehose effect, including, but not limited to
digests and setting up your client to move mailing list post
Just an observation. I've been a member of this mailing list since
(literally) five days ago and I am receiving a busload of emails.
I'm a member of Stackoverflow and I visit the Q&A site daily... and I
hardly ever receive emails.
I suspect Discourse would be a good match for these discussion
On 17/09/18 20:10, Eric V. Smith wrote:
See also PEP 501, which could be used for i18n.
My first idea was to propose a t-string (for translatable string).
Cheers,
Hans
___
Python-ideas mailing list
Python-ideas@python.org
https://mail.python.org/ma
On 17/09/18 19:42, Stephen J. Turnbull wrote:
> That's why I would like to see a parameter that can be passed to
> the f-string.
This doesn't make sense to me.
If I get a request in English, I need to return English.
If I get a request in French, I need to return French.
# At the start of
I don't see how this immediately helps the OP, who wants a *literal*
expression that automatically invokes the translation machinery as
well as the interpolation machinery.
Actually, no, I do not want the expression to be automatically
translated at compile time. It should be translated at run
On 17/09/18 09:53, Niki Spahiev wrote:
Is it possible to use f-strings when making multilingual software?
When i write non-hobby software translation is hard requirement.
At this moment, it seems that this is not possible.
My use case is not very unique and that's why I wrote the proposal in
at 7:02 PM, Hans Polak wrote:
I have recently updated my code to use the more pythonic f-string instead of
'{}'.format()
Well there's your problem right there. Don't change your string
formatting choice on that basis. F-strings aren't "more Pythonic" than
eith
I have recently updated my code to use the more pythonic f-string
instead of '{}'.format()
Now, I want to start on the road to multilingual internationalization,
and I run into two problems. The first problem is that f-strings do not
combine with i18n. I have to revert to the '{}'.format() sty
10 matches
Mail list logo
