2. care to elaborate ?
3. it's not divided, it's evolving from 2 to 3. Java's community is under Oracle's grip, don't know if it's any better...
4. it's not because you can do it that it's worth to do it, so in practice API are just not changing at runtime
5. I can say the same of my industrial strength Java environment...
6. Not a problem since what you do doesn't require speed
7. Ever used PyCharm ? I wouldn't say it's poor tooling. The debugger is fine. What I miss is something like a good profiler to look at running code.
But I'd say :
8. Optional typing should've been there from day one, it'd made code editor, tooling better
9. The date/time handling is not good
10. SOA support is weak (and in the kind of setting I am, we use tons of XSD, WSDL, XML, security, signature you name it)
For example, rather than checking if a dictionary has an element before accessing it, you just try to access it and handle the KeyError if it doesn't. The code reads easier and the normal flow would be faster in this case.
When used in EAFP context only, I think it is fine to use exceptions as part of logic in Python. They are relatively less costly compared to C.
vprof is quite nice: https://github.com/nvdv/vprof
Sklearn, tensorflow, pandas, Sqlalchemy, requests, Beautifulsoup, numpy, scipy, pulp.
If you have a language that had equivalent libraries that cover all these domains I'd love to hear it. Until then I can build really cool stuff in Python very easily thanks to the amazing hardwork and generosity of these library creators.
R[1].
One of the main reasons I like python is that it is the most self-documenting language I've come across. Say what you like about significant whitespace, but in my last job I used to show salespeople snippets of code and they understood them - with no knowledge of the language.
[1]: https://www.python.org/dev/peps/pep-0257/I'm using Python since about half a year and for all I did this wasn't an issue. I just started with 3 and had the feeling everything around me was 3 as well. 3 was released in '08.
http://effbot.org/pyfaq/why-does-python-use-methods-for-some...
I guess is that.
deque
defaultdict
Counter
After many years I often write DefaultDict myself.Edit: formatting
Admittedly it is mildly annoying when someone decides to use some random number of spaces for indentation, and you have to fix it to make it match the rest of your code (my preferred editor, Geany, has a feature for this). We should all just use tabs. But "very hard"?
This probably reads pedantically, but I do think there's a distinction. By analogy, if someone tried to post APL on a site that didn't support Unicode, you wouldn't say the issue is it's "hard to cut and paste APL".
In addition to the points posted in a parallel thread, selecting and copying leading whitespace reliably is more difficult than just getting the printable characters. Also: it's not something that anyone has any cause to do outside of copying Python text.
(If neither happens, then I guess it isn't really a problem.)
There is no formal definition of the language. It is defined by the C implementation. So I'm not sure how meaningful that distinction is.
> If neither happens, then I guess it isn't really a problem.
Or people give up on Python and use another language.
The real-world distinction between the Python specification and its implementation started in the late 1990s, with JPython (now Jython).
1. In-consistant syntax.
2. The language uses exceptions to control flow of logic.
3. Divided community, since Python 3+ included breaking changes to the standard.
4. Un-discoverable APIs. You better hope the documentation is bulletproof else the API could change in any which way during runtime.
5. Poor error messages. If an import goes wrong you are not told why, and so on.
6. Ultimately slow performance for anything marginally complex.
7. Poor tooling.