will fix it if it breaks" (which is how the
existing stdlib works) to "we approve these *people* (the people working
on requests or regex or whatever) and we will cease to do if they break
their code".
--
Brendan Barnwell
"Do not follow where the
)`. Or you can just give c an attribute that's a dict,
but has an easier-to-type name than __dict__, so you can do
`c.mydict[T]`. What is the specific advantage of `c.[T]` over these
existing solutions?
--
Brendan Barnwell
"Do not follow where the path may lead. Go, instead, where there is no
some task.
--
Brendan Barnwell
"Do not follow where the path may lead. Go, instead, where there is no
path, and leave a trail."
--author unknown
___
Python-ideas mailing list
Python-ideas@python.org
https://mail.python.org/mailman/listin
ese infinite iterators
were fixed so they could be interrupted, this containment problem would
be much less painful.
--
Brendan Barnwell
"Do not follow where the path may lead. Go, instead, where there is no
path, and leave a trail."
--author unknown
Python
without looking up how to write comments" as a useful goal. As with
.join(), once you learn that Python uses #, you know it, and it's not
really a problem. Also, as someone else mentioned, // is a valid
operator in Python, making its use as a comment marker potentially
ambiguous.
--
Br
tion message at all by default (since the object might have a long
__str__ that would be irritating). It would just be there, attached to
the exception, so that it could be used if needed.
--
Brendan Barnwell
"Do not follow where the path may lead. Go, instead, where there is no
path, and
e that may or may not outweigh the performance hit.
--
Brendan Barnwell
"Do not follow where the path may lead. Go, instead, where there is no
path, and leave a trail."
--author unknown
___
Python-ideas mailing list
Python-ideas@python.org
htt
tring into a nicely
manipulable Path object that allows various handy path operations.
--
Brendan Barnwell
"Do not follow where the path may lead. Go, instead, where there is no
path, and leave a trail."
--author unknown
___
Python-ideas
. But I don't see why it couldn't take
multiple arguments as you suggest.
--
Brendan Barnwell
"Do not follow where the path may lead. Go, instead, where there is no
path, and leave a trail."
--author unknown
___
Python-ideas mailing li
e leftmost operand would be enough to give you
nice syntax for chaining all the rest.
--
Brendan Barnwell
"Do not follow where the path may lead. Go, instead, where there is no
path, and leave a trail."
--author unknown
___
Python-idea
On 2017-05-14 00:34, Chris Angelico wrote:
On Sun, May 14, 2017 at 2:53 PM, Brendan Barnwell <brenb...@brenbarn.net> wrote:
Attributes aren't just for passing things to other methods. They're
for storing state. In your proposed system, how would an object mutate one
of i
tion arguments to assign to local names. But if you could start
putting other things as function arguments, you could use them to assign
to things that are not local names. That is a major change.
--
Brendan Barnwell
"Do not follow where the pat
what matters is not the frequency rank but the magnitude of the
separation in frequency between the outliers and the nonoutliers. But
that's a much subtler notion than just "least common".
--
Brendan Barnwell
"Do not follow where the path may lead. Go, instead, where ther
as what he said. The point is that if they
*are* the same object, you *don't* need to check equality.
--
Brendan Barnwell
"Do not follow where the path may lead. Go, instead, where there is no
path, and leave a trail."
--author unknown
___
Py
d messages.
--
Brendan Barnwell
"Do not follow where the path may lead. Go, instead, where there is no
path, and leave a trail."
--author unknown
___
Python-ideas mailing list
Python-ideas@python.org
https://mail.python.org/mailman/listin
rent assignment
> operators.
The thing is that a =+ 5 is already valid syntax, and means the same as
a = +5. You don't need spaces around operators in Python. So your
proposal would have the change the behavior of existing syntax, which
pretty much makes it a nonstarter.
--
Brendan
a finally where the yield is in the try.
--
Brendan Barnwell
"Do not follow where the path may lead. Go, instead, where there is no
path, and leave a trail."
--author unknown
___
Python-ideas mailing list
Python-ideas@python
what we wanted was to able to use
recurrence relations, your proposal would be insufficient.
--
Brendan Barnwell
"Do not follow where the path may lead. Go, instead, where there is no
path, and leave a trail."
--author unknown
___
Py
hat header
columns are present, or skip some number of rows), and then resumes.
This would increase the burden of updating code to adapt to the new
breakage (since in this case the programmer would likely have to, or at
least want to, think about what is going on rather than just blindly
wrapping e
e kinds of things" I mean doing them more in a
more conise way without an extra level of iteration. (You can "do
multiplication" by adding repeatedly, but it's still nice to have
multiplication as an operation.)
--
Brendan Barnwell
"Do not follow where the path may lea
up with the
Unicode consortium. (Good luck with that.)
--
Brendan Barnwell
"Do not follow where the path may lead. Go, instead, where there is no
path, and leave a trail."
--author unknown
___
Python-ideas mailing list
Python-ideas@pyth
My position (reiterated by the text you
quote from Steven D'Aprano) is not that Python is used only by
generalists. It is that we shouldn't change Python in a way that ONLY
helps specialists.
--
Brendan Barnwell
"Do not follow where the path may lead. Go, instead, where there is no
ame reason. Those notations are not useful enough
to justify their existence. Hexadecimal is more justifiable as it is
far more widely used, but I would be more open to removing hexadecimal
than I would be to adding octal.
Also, "L" as a long-integer suffix is already gone in P
de rigeur
in the physical science community isn't enough. I would want to see
some actual attempt to quantify how much benefit there would be in the
PYTHON community (which of course includes, but is not limited to, those
using Python for physical-science computations).
--
Brendan Barnwe
ime rather than
being a constant, but again, the point of f-strings is to make things
like that writable as strings in source code. If you don't want to
write them as strings, you can still concatenate separate string values
or use various other solutions.
--
Brendan Barnwell
"Do not follow
o ordinary
expressions.
--
Brendan Barnwell
"Do not follow where the path may lead. Go, instead, where there is no
path, and leave a trail."
--author unknown
___
Python-ideas mailing list
Python-ideas@python.org
https://mail.python.org/mai
201 - 226 of 226 matches
Mail list logo
