341–350 of 381 posts
Earlier quoted context omitted.
Forunately, tauthon is a community-supported fork of Python 2.7 so that we may continue using the best version indefinitely.
You'll be laughed out of future interviews if you mention your interest in that project.
Earlier quoted context omitted.
Not OP, but maybe it's "as": if re.match(pattern, string) as m: #use m Seems a bit more Pythonic, as "as" is already used like this with "with". Either one would be fine with me and useful.
It's already used in imports as well! It was the better choice, I don't know which arguments convinced them otherwise
Earlier quoted context omitted.
> As a developer who has primarily developed applications in Python for his entire professional career, I can't say I'm especially excited about any of the "headlining" features of 3.8. Python is a fairly old, mature language. What features would you have been especially excited about?
I wouldn’t mind cpython performance improvements over language features. Specifically startup time. Py cli tools can easily take up to 300-600ms to start. Now, try to use them for scripting. A single script doing a bunch of calls to python clis has already several seconds of runtime penalty.
I wonder if there is anything that can really be done, outside of something like Cython.
Earlier quoted context omitted.
Because if you need to branch based on type more than a few times in your function it can get pretty hard to read. Am I right that the basis of your complaint is that it's now harder to find all the members of (what you'd call in C++) the "overload set" for a particular function? If so I can see your point.
Yes, that's my point. And it doesn't really simplify the function itself, it just rearranges it, in the same way you can break up a complex painting into jigsaw pieces and say, "Look, each piece is simple!"
Earlier quoted context omitted.
Yes, "path dependence" is a good way to describe it. (And Python has been my favorite language for 16+ years now) For https://www.oilshell.org/ , which has Python/JS-like functions, I chose to use Julia's function signature design, which is as expressive as Python's, but significantly simpler in both syntax and implementation: Manual: https://docs.julialang.org/en/v1/manual/functions/index.html... Comparison: https:/…
But the Julia syntax can not represent arguments that can be passed either positional or named, right?
There was a rule in Google's style guide that said to only pass optional arguments with names, and required args without names. It basically enforced this separation while being slightly less flexible, because you can't have optional positional args or required named args.
Tens of millions of lines of code was written by thousands of programmers in that style, and it caused no problems at all. On the contrary it made code more consistent and readable.
Earlier quoted context omitted.
It's already used in imports as well! It was the better choice, I don't know which arguments convinced them otherwise
I think I remember seeing something about the "as" syntax. Wish I could find what I read, IIRC some arguments convinced me that the walrus operator was an improvement.
https://www.python.org/dev/peps/pep-0572/#alternative-spelli...
Earlier quoted context omitted.
What's the value of a sorted map over an ordered map? I don't think I've ever cared to iterate over map values based on the alphanumeric ordering of their keys.
In Haskell we use sorted maps as persistent data structures. Persistent in this context means that the insert-method returns a new map and the old map is still around, if you need it. It's basically copy-on-write. The old and new map share all but O(log n) data. You could probably do something like that with an unsorted map, but it's a good fit for a sorted one.
Earlier quoted context omitted.
> nice mnemonics like these: > option-w ∑ This would grate on me every single time I had to use it. It's an S. Put it on option-s.
For context opt s is ß so the decision wouldn’t be easy if you want to include both.
Putting double S on option-s just makes option-w for Sigma more grating. If they were going by shape, it'd be on option-b, which is equally stupid. But since it's on S, we can conclude that... someone at Apple knows German, but nobody can even name a Greek letter? That Germans are right and Greeks are wrong? What?
Earlier quoted context omitted.
You'll be laughed out of future interviews if you mention your interest in that project.
Some people use software as a tool and aren't zealots about versions or constantly chasing updates.
"Getting shit done" doesn't happen if you can't move forward eventually. I'd have substantial concerns hiring someone who can't get over Python 2.7.
Earlier quoted context omitted.
For context opt s is ß so the decision wouldn’t be easy if you want to include both.
What are á and à? Putting double S on option-s just makes option-w for Sigma more grating. If they were going by shape, it'd be on option-b, which is equally stupid. But since it's on S, we can conclude that... someone at Apple knows German, but nobody can even name a Greek letter? That Germans are right and Greeks are wrong? What?