[issue40477] Launcher on Catalina
New submission from Werner : I can’t figure out how to use Python Launcher on Catalina. Or it is broken. Anyway: It does absolutely nothing. When I double click a scriopt file, I se very shortly the preferences window of Launcher, and this is all. The script is not executed. I made a very simple script which writes a small text file. The script works flawlessly, when I call it in the terminal, but the Launcher seems not even to open it. Is this a bug with Catalina, or what is to be done? -- components: macOS messages: 367935 nosy: Auerhahn, ned.deily, ronaldoussoren priority: normal severity: normal status: open title: Launcher on Catalina versions: Python 3.8 ___ Python tracker <https://bugs.python.org/issue40477> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40477] Launcher on Catalina
Werner added the comment: Thank you! That’s an Information which Looks bad but has good parts. At least it may be not my fault ;) Best regards Werner Hintze Am 2. Mai 2020, 19:10 +0200 schrieb Ned Deily : > > Ned Deily added the comment: > > Thanks for the report. At first glance, it does look like it's broken on > macOS 10.15. I'll look into it. > > -- > assignee: -> ned.deily > > ___ > Python tracker > <https://bugs.python.org/issue40477> > ___ -- ___ Python tracker <https://bugs.python.org/issue40477> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40477] Python Launcher app on macOS 10.15 Catalina fails to run scripts
Werner added the comment: I believe, I found a simple way to get what you are looking for: Open Automator and create an app. Select »execute Shell script« put in the editor: python3 $1 Save this as MyPythonLauncher or what you want. Test it: Drop a Python script on the app. It should execute without opening the Terminal (at least if it is a GUI-script). If this is not clear, write me on we.hin...@gmail.com -- Werner Hintze • Auerstraße 1 • 10249 Berlin Tel.: +49 30 42 73 486 • Mobil: +49 160 94 68 76 60 Am 16. Mai 2020, 06:58 +0200 schrieb Ned Deily : > > Ned Deily added the comment: > > > After your final fix, if I understood you correctly, we will no longer have > > to open Terminal? > > That's correct. That's the way the Launcher works on previous version on > macOS. > > > will it ever be possible to not have the terminal run in the future? > > That's the way the Launcher works. It's a very simple-minded application. > Essentially all it does for you is to provide an easy way from the Finder to > run a Python script in a terminal window, i.e. by double-clicking or by > drag-and-drop. Like on other Unix-based systems, Python on macOS is typically > used as a command line program that runs under a Unix shell in a terminal > window of some sort. Python itself does not provide a macOS GUI application > interface; that is something that IDLE does (and other third-party IDEs that > support Python). The Launcher app dates back to the very earliest days of Mac > OS X when Python for Classic MacOS (System 9) was ported over. The Launcher > is not really used very much as far as I can tell and its age shows with some > usability and even security concerns. If you are comfortable using a terminal > window and a Unix shell, you may find it more convenient to just run scripts > directly there rather than indirectly using the Launcher, e.g. > > $ cd Documents # or whatever Folder > $ python3.8 your_script.py > > Or, to open Python in interactive mode, where you can enter statements and > immediately see the results: > > $ python3.8 > > If you prefer a full-featured dev environment, you can use IDLE. > > > Is there no way to edit a previous comment? > > On the current bugs.python.org, no, sorry! > > > the Launcher Preferences window also opens when I run a script. Did I miss > > a setting? > > As far as I know, opening Preferences is a "feature" of the Launcher and > can't be prevented. > > -- > > ___ > Python tracker > <https://bugs.python.org/issue40477> > ___ -- ___ Python tracker <https://bugs.python.org/issue40477> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2561] Instance remembers old values from former life
New submission from Werner Arnhold <[EMAIL PROTECTED]>: I don't know if it is a bug or a feature but the result seems to be wrong for me: A constructor argument remembers its values from the last call -- files: class_with_listparamdefault.py messages: 65024 nosy: warnhold severity: normal status: open title: Instance remembers old values from former life type: behavior versions: Python 2.5 Added file: http://bugs.python.org/file9959/class_with_listparamdefault.py __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2561> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue31990] Pickling deadlocks in thread with python -m
Change by Werner Smidt : -- status: pending -> open Removed file: https://bugs.python.org/file47255/testqueuepickle.py ___ Python tracker <https://bugs.python.org/issue31990> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue31990] Pickling deadlocks in thread with python -m
Werner Smidt added the comment: The condition still stands. if I execute: python3 testqueuepickle3.py Everything is fine. If, however I execute: python3 -m testqueuepickle3.py It hangs. -- versions: +Python 3.8 ___ Python tracker <https://bugs.python.org/issue31990> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue31990] Pickling deadlocks in thread with python -m
Werner Smidt added the comment: Sorry for being lacking in providing some OS info. b Opensuse Tumbleweed, Linux kernel 5.8.10-1, Intel system I cannot explain why, but relating to Sara's answer, if you remove the .join() statements at the end, you get the following exception: /usr/bin/python3: Error while finding module specification for 'testqueuepickle3.py' (ModuleNotFoundError: __path__ attribute not found on 'testqueuepickle3' while trying to find 'testqueuepickle3.py') mynamedtuple(param1='INSIDE thread', param2='namedtuple') So I guess that it gets stuck after an exception is thrown? If I call it Sara's way, there is no exception thrown. Sorry, I know this is a very specific case, but I thank you both for taking the time to contribute :-) -- ___ Python tracker <https://bugs.python.org/issue31990> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue31990] Pickling deadlocks in thread with python -m
Werner Smidt added the comment: Thanks for going to the trouble, Sara. Curiosity remains, but I'll mark this as closed. -- stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue31990> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue31990] Pickling deadlocks in thread with python -m
New submission from Werner Smidt : Hi there I recently stumbled on an interesting behaviour. I won't call it an error, because I think it's a mistake I made. BACKGROUND: I want to spawn threads that handle pickled data. This works really well. However, I would like to execute the python script in question as a module, i.e. python -m mymodule. This is merely for aesthetic purposes. The attached script has two functions: 1. Pickle/unpickle an instance of a `namedtuple` 2. Pickle/unpickle a string Each of these functions are run in the main thread and then in subsequent spawned threads. If I run the script attached with "python testqueuepickle.py", it works fine. I get the data pickled/unpickled in the respective functions and nothing deadlocks and everything is printed to screen. If, however, I run it with the "-m" option (python -m testqueuepickle.py) , the program deadlocks at the pickling of the "namedtuple" instance. The pickling/unpickling of the string appears to be unaffected. Programming practices aside, what do you think could be the cause of this? -- files: testqueuepickle.py messages: 305953 nosy: Werner Smidt priority: normal severity: normal status: open title: Pickling deadlocks in thread with python -m type: behavior versions: Python 2.7 Added file: https://bugs.python.org/file47255/testqueuepickle.py ___ Python tracker <https://bugs.python.org/issue31990> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14810] Bug in tarfile
New submission from Hans Werner May : Bug in tarfile: In extractall, when a file exists in tarball with changetime older than (I don't know, in my case it was year 1956) tarfile raises an Overflow exception: File "/usr/lib64/python2.7/tarfile.py", line 2298, in utime os.utime(targetpath, (tarinfo.mtime, tarinfo.mtime)) OverflowError: Python int too large to convert to C long System: Mageia 1.0 Python version: 2.7.1 -- messages: 160674 nosy: hwm priority: normal severity: normal status: open title: Bug in tarfile versions: Python 2.7 ___ Python tracker <http://bugs.python.org/issue14810> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14810] Bug in tarfile
Hans Werner May added the comment: "Out of curiosity: where did you get a file that was last modified in 1956?" No idea, this was a jpeg file, probably downloaded from internet. Btw, on Linux you can manipulate the creation date with the touch command, so it is possible to create a tarball with a member which has creation date 1956, but it is not possible to extract it with the extractall method. -- ___ Python tracker <http://bugs.python.org/issue14810> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13952] mimetypes doesn't recognize .csv
Werner Van Geit added the comment: Will this patch ever make it into the main python version ? I just ran into exactly this issue (mimetypes returns None as mimetype of csv file on Windows) -- nosy: +Werner Van Geit versions: +Python 3.4, Python 3.5, Python 3.6 ___ Python tracker <http://bugs.python.org/issue13952> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
