pansa2

62 ms·

751.
by pansa2 6y ago
> You might be looking at the wrong language for that. You’re right, Python is not a simple language at all. Yet that’s how it’s widely perceived - I’m not sure why.
752.
by pansa2 6y ago
Visual J++? > Some observers have remarked that this incompatibility appears to have been a deliberate aim of Microsoft's, in an attempt to at least slow the advance of Sun's Java technology. https://en.wikipedia.o
753.
by pansa2 6y ago
> The Python Steering Council and Python Software Foundation will work together to contract a developer This would represent a significant increase in the number of people paid to work on the Python language. Two years ago it was estim
754.
by pansa2 6y ago
> There is nothing to add to it. I'm not sure that's true. Maybe LuaJIT was never going to add the features it's missing from Lua 5.2, 5.3 and 5.4. However, when Mike Pall stepped back in 2015 [0], he had still been plan
755.
by pansa2 6y ago
Relevant: > > Threaded code should have better branch prediction behavior than a jump table with a single dispatch point > This is not the case anymore, at least for modern Intel processors. Starting with the Haswell micro-archi
756.
by pansa2 6y ago
I don’t think it’s unexpected for an augmented assignment operator to do an assignment. It is unexpected for it to instead call `extend`. It’s even worse to do the first for some types and the second for other types.
757.
by pansa2 6y ago
Yes - in many languages x is a new variable on each iteration of the loop. Python re-uses the same variable each time, because the loop does not have its own scope.
758.
by pansa2 6y ago
I think the reason not to write `== None` is that classes can override `==`: class C: def __eq__(self, other): return True C() == None # True C() is None # False
759.
by pansa2 6y ago
Yeah, IME `is None` is by far the most common use of `is`. I don’t think many people would miss `is` if it were removed and an `is_none` function introduced.
760.
by pansa2 6y ago
You’re right - I’m not suggesting that `+` should work in-place, but that `a += b` should do the same thing as `a = a + b` and not work in-place.
761.
by pansa2 6y ago
It’s because `another_tuple[2] += [99, 999]` is equivalent to something similar to `another_tuple[2] = another_tuple[2].__iadd__([99, 999])`. The list is modified in __iadd__ but then the assignment fails. The assignment is necessary in cas
762.
by pansa2 6y ago
I guess reference counting makes copying a list in Python a much more expensive operation than it would be in other languages. Although perhaps it could also be used to avoid copying in cases where the list's own reference count is e
763.
by pansa2 6y ago
>>> another_tuple ([1, 2], [3, 4], [5, 6, 1000]) >>> another_tuple[2] += [99, 999] TypeError: 'tuple' object does not support item assignment >>> another_tuple ([1, 2], [3, 4],
764.
by pansa2 6y ago
I assume most game development (or, at least, game engine development) is still in C++? How easy would it be to start moving parts of it to Rust? For example, if I were to write a library (e.g. a physics engine) in Rust, how easy is it fo
765.
by pansa2 6y ago
> A big reason why I got into Python was because it’s the language that can be “read by anyone”, even those who do not know Python. Yes! For the first 2 decades of its life, people loved Python because it was like “executable pseudocod
766.
by pansa2 6y ago
Ah yes, you’re right.
767.
by pansa2 6y ago
Go has a different kind of complexity from Python, though. It makes you deal with low-level details like pointers and casting between different-sized integers, none of which are necessary in Python.
768.
by pansa2 6y ago
> this is a post from 16 years ago Sure, but the only opportunity to change this was along with the other breaking changes in Python 3.0, which is now 12 years old.
769.
by pansa2 6y ago
My concern with Python’s feature bloat is the opposite. That there aren’t parts you’re not supposed to use - developers are expected to know all of it. Three string formatting approaches are all in wide use. There are now two different ways
770.
by pansa2 6y ago
Really? It’s best practice to use a magic number rather than a name? That breaks one of the most fundamental rules for writing good code.
771.
by pansa2 6y ago
Pattern matching will definitely make Python harder to learn, though. It’s not particularly coherent with the rest of the language either - the match statement has been described as “a DSL contrived to look like Python, and to be used insid
772.
by pansa2 6y ago
What’s wrong with the OOP syntax?
773.
by pansa2 6y ago
In that case, what’s the correct way to write a clause that only matches if `status` is equal to 404? Do we have to use the integer literal 404 instead of a named integer?
774.
by pansa2 6y ago
In those other languages, if `not_found` is equal to 404 before the match block, how do you write a clause that only matches if `status` is 404? Do you have to use the integer literal 404 instead of the named integer `not_found`?
775.
by pansa2 6y ago
Guido has been strongly opposed to the use of tagged integers: https://mail.python.org/pipermail/python-dev/2004-July/04614...
776.
by pansa2 6y ago
> Are you sure the second one isn’t just declaring not_found as a stand-in for 404 That's what it looks like, but no, the refactoring really does change an equality test into an assignment.
777.
by pansa2 6y ago
There are some exceptions to this - for example, the iteration variable(s) in a list comprehension are only in scope within the comprehension.
778.
by pansa2 6y ago
Mutates it. Python `match` statements do not introduce a new scope.
779.
by pansa2 6y ago
> Exactly half of all responders, forming nearly 90% of the above majority, are fine with that form being PEP 634. That half includes those who voted for "accept 634 + 640" or "accept 634 + 642", whom I doubt are en
780.
by pansa2 6y ago
Is that not a reasonable sample of the 87 core developers eligible to vote? https://discuss.python.org/groups/committers

More ›