71–80 of 150 posts
Python 1.0 is great because back then you don't need to worry about the Python2/3 issue. :)
Is it still an issue really? :/ Have been using Python 3 exclusively in production since about a year ago and it really seems like the whole 2/3 thing is starting to blow over. I haven't found any packages I need that aren't 3 compatible and porting to 3 was really way easier than people had made it out to be.
Earlier quoted context omitted.
Is it still an issue really? :/ Have been using Python 3 exclusively in production since about a year ago and it really seems like the whole 2/3 thing is starting to blow over. I haven't found any packages I need that aren't 3 compatible and porting to 3 was really way easier than people had made it out to be.
Yes. Very much still an issue. There's mountains of Python 2 code still out there and loads of software starts with Python 2 and then maybe adds Python 3 support later. Hopefully. For example [issue #1]( https://github.com/tensorflow/tensorflow/issues/1 ) for Tensorflow - one of the most popular Python packages out there is "add Python 3 support". It's one of the biggest reasons not to use Python IMO. No other popula…
Py2/3 is not an issue in practice.
Interesting to read his description of the language, which sounds pretty much exactly like python is now. It’s a pretty good testament to why python gained and retained popularity. Though not without fault, python is certainly one of the best-designed languages ever created, in my opinion.
There's a lot I like about Python, but there are a couple of things that they've gotten so horribly wrong. 1. The KeyboardInterrupt exception for SIGINT. Whoever came up with that idea destroyed the credibility of the entire interpreter. Python falls flat on its face to me because of this one design choice. It's impossible to write a Python script that will not dump a full debug stack trace if you send SIGINT (ie: Ct…
% python -c pass
^CTraceback (most recent call last):
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site.py", line 62, in
import os
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/os.py", line 400, in
import UserDict
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/UserDict.py", line 83, in
import _abcoll
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/_abcoll.py", line 9, in
"""
KeyboardInterrupt
One of the workarounds was to do:
python -S
(Another request for this feature is at https://bugs.python.org/issue24261 .)
If you are still working with Python, and still want this feature, you might contribute to that second thread. The first is rather contentious.
Want to play with it? conda create -n py1 python=1.0 source activate py1 python Python 1.0.1 (Mar 26 2014) Copyright 1991-1994 Stichting Mathematisch Centrum, Amsterdam >>> Sorry Windows, only on macOS and Linux.
Does this not work with Ubuntu on Windows? I've been using it as my primary development environment and it seems to work perfectly with the mainstream Ubuntu/linux software I deal with. https://docs.microsoft.com/en-us/windows/wsl/about
Python 1.0.1 (Mar 26 2014)
Copyright 1991-1994 Stichting Mathematisch Centrum, Amsterdam
Segmentation fault (core dumped)
(gdb) bt
#0 0x00000000004212bb in do_mkvalue ()
#1 0x00000000004210a7 in do_mktuple ()
#2 0x00000000004211a8 in do_mkvalue ()
#3 0x00000000004213f2 in vmkvalue ()
#4 0x00000000004214a1 in mkvalue ()
#5 0x0000000000422438 in err_input ()
#6 0x000000000042258c in parse_file ()
#7 0x00000000004226ae in run_file ()
#8 0x0000000000422bf3 in run_script ()
#9 0x000000000042232a in realmain ()
#10 0x00000000004039f4 in main ()Interesting to read his description of the language, which sounds pretty much exactly like python is now. It’s a pretty good testament to why python gained and retained popularity. Though not without fault, python is certainly one of the best-designed languages ever created, in my opinion.
There's a lot I like about Python, but there are a couple of things that they've gotten so horribly wrong. 1. The KeyboardInterrupt exception for SIGINT. Whoever came up with that idea destroyed the credibility of the entire interpreter. Python falls flat on its face to me because of this one design choice. It's impossible to write a Python script that will not dump a full debug stack trace if you send SIGINT (ie: Ct…
I never noticed that but now that you say it...
There should be a way to pass an option to Python so that if you do 'python --early-sigint "message"' it prints the message for an early sigint.
You should post that to the python-ideas mailing list. It's a long and tedious process to get everyone on board by writing mails, but it works. Pretty much everyone can do it.
Earlier quoted context omitted.
The fact that almost everything in Python is mutable by default pretty much guarantees the GIL is never going away.
That doesn't affect other languages with similar semantics. Not even alternative Python implementations for that matter.
Earlier quoted context omitted.
Does this not work with Ubuntu on Windows? I've been using it as my primary development environment and it seems to work perfectly with the mainstream Ubuntu/linux software I deal with. https://docs.microsoft.com/en-us/windows/wsl/about
While we fix bugs in our Linux packages so they work on USW/WSL this one appears to have problems (and I do not expect I will look into them any time soon): Python 1.0.1 (Mar 26 2014) Copyright 1991-1994 Stichting Mathematisch Centrum, Amsterdam Segmentation fault (core dumped) .. I did capture the backtrace though; for what it's worth: (gdb) bt #0 0x00000000004212bb in do_mkvalue () #1 0x00000000004210a7 in do_mktup…
python -c "print 'hello world'"Earlier quoted context omitted.
That doesn't affect other languages with similar semantics. Not even alternative Python implementations for that matter.
Which other language shares Python's level of dynamism - where object attributes can be conditionally deleted at runtime, for example - and manages to have convenient thread-safe operations?
And as I said, Jython and IronPython also don't have a GIL.
Interesting to read his description of the language, which sounds pretty much exactly like python is now. It’s a pretty good testament to why python gained and retained popularity. Though not without fault, python is certainly one of the best-designed languages ever created, in my opinion.
There's a lot I like about Python, but there are a couple of things that they've gotten so horribly wrong. 1. The KeyboardInterrupt exception for SIGINT. Whoever came up with that idea destroyed the credibility of the entire interpreter. Python falls flat on its face to me because of this one design choice. It's impossible to write a Python script that will not dump a full debug stack trace if you send SIGINT (ie: Ct…
Earlier quoted context omitted.
Yes but "sucking so bad its not even funny" is still superior to maven and ant (and as another user mentioned, pipenv is a very good approximation of Cargo, which is a really good build and package management system).
I would take Maven and Ant any day over having to play with virtual environments, multiple Python installations and Python 2/3 dictonomy.
If you need to use Python again, look at pipenv – it automates all of that for you down to one command, similar to e.g. Rust’s cargo: