191–194 of 194 posts
Earlier quoted context omitted.
Except, you often need a full compiler toolchain for all the c dependencies. Then you need to make sure you have the required header files. Then you try and deploy to a small EC2 instance and run out of RAM building lxml or similar.
If your requirements are advanced, make packages on your dev box then deploy those: https://nylas.com/blog/packaging-deploying-python
Earlier quoted context omitted.
1. By people you mean "Google", and with a whole lot of money and a room full of some of the smartest people they could find. V8 is a whole department working full time, not a open source community-led effort. JS is also a different beast in a whole lot of ways. No, I am definitely saying " we can't make a JIT for Python that doesn't significantly impact single threaded scripts, retains significant backwards compatib…
You're making it sound like you're disagreeing with me but it sounds like we're in complete agreement on the main point: it's not impossible to create a cPython JIT. It's a choice whether to do it or not. (And by the way, creating a JIT is a piece of engineering, it's not black magic). It's fair enough if people think that would be the wrong choice, I might even agree actually, but if the cPython developers say, time…
It's not that the Python developers preventing discussion, it's just this discussion is always fruitless, has been had many times before and the people invoking the discussion often blame the cPython developers for their response. Nobody wins, it's a waste of time.
I used to write a lot of personal Python scripts (ie ~/bin). I mainly did this because I seem to always screw up bash scripts and just can't remember all the conditional flags ie ([[-z ]] and error handling with bash for me has always been tricky. However in the last couple of years I have dropped Python in favor of Groovy in part because I know the JVM and its plethora of libraries so well. Groovy is a highly underr…
> I really don't have to worry if I write Groovy in a pre Java 5 (ie without generics) Groovy has many incompatible changes between versions, esp from 1.8 to 2.0 but also 1.7 to 1.8, 1.6 to 1.7, etc. Many sites provide Groovy 1.8 as the default because no-one there wants to bother with upgrading.
I am also not as Groovy as I could be (ie write like its Java at times) so maybe thats why I haven't ran into issues.
Earlier quoted context omitted.
The difference is that most people can read most other peoples' python code. Perl didn't tend to have that quality. EDIT Added another "most" to make it clear that not everyone can write readable python.
That depends entirely on who is writing the code. I have seen some truly awful Python as well as truly awful Perl.