Mailman 3 - Python-list

Re: Python
by Dan Espen Dec. 17, 2025

Dec. 17, 2025

Lawrence D’Oliveiro <ldo(a)nz.invalid> writes: > On Mon, 15 Dec 2025 12:57:57 +0000, mm0fmf wrote: > >> On 14 Dec 2025 11:56:42 GMT, Stéphane CARPENTIER wrote: >> >>> My issues with python are: >>> - It's using indentations, so when I comment a block of code to see >> >> ''' and ''' are your friend > > Unless the block has triply-quoted strings inside it ... Then """ and """ are your better friends. -- Dan Espen

2 1

Re: Python
by rbowman Dec. 17, 2025

Dec. 17, 2025

On Tue, 16 Dec 2025 21:45:42 -0000 (UTC), Lawrence D’Oliveiro wrote: > On Mon, 15 Dec 2025 12:57:57 +0000, mm0fmf wrote: > >> On 14 Dec 2025 11:56:42 GMT, Stéphane CARPENTIER wrote: >> >>> My issues with python are: >>> - It's using indentations, so when I comment a block of code to see >> >> ''' and ''' are your friend > > Unless the block has triply-quoted strings inside it ... Yeah, well. I've been burned more than once by someone who added /* stupid comment */ someplace west of the 80th column in the code.

2 2

Re: Python
by mm0fmf Dec. 17, 2025

Dec. 17, 2025

On 14/12/2025 23:29, Lawrence D’Oliveiro wrote: > On 14 Dec 2025 11:56:42 GMT, Stéphane CARPENTIER wrote: > >> My issues with python are: >> - It's using indentations, so when I comment a block of code to see ''' and ''' are your friend And maybe stop using edlin etc. and invest in a modern editor that knows the language and so helps you by making life easier.

13 13

Issues compiling Python 3.14.2 on Rhel 8.10
by Mads Boye Dec. 16, 2025

Dec. 16, 2025

Hi. I am currently facing issues compiling Python 3.14.2 on my RHEL 8 server. It seems to relate to the --enable-optimizations argument. If I build with out the --enable-optimizations it is finalizing the build, but with the argument, it segfaults during the "test_functools" ./configure not working: ./configure --prefix=/home/easybuild/Python-3.14.2-GCCcore-14.3.0 --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --enable-shared --with-lto --enable-optimizations --with-ensurepip=upgrade Error output: 0:01:04 load avg: 1.61 [17/43] test_fstring passed 0:01:04 load avg: 1.61 [18/43] test_functools Fatal Python error: Segmentation fault Current thread 0x000015555553af80 [python] (most recent call first): File "/home/easybuild/Python-3.14.2/Lib/test/test_functools.py", line 451 in test_recursive_pickle File "/home/easybuild/Python-3.14.2/Lib/unittest/case.py", line 615 in _callTestMethod File "/home/easybuild/Python-3.14.2/Lib/unittest/case.py", line 669 in run File "/home/easybuild/Python-3.14.2/Lib/unittest/case.py", line 725 in __call__ File "/home/easybuild/Python-3.14.2/Lib/unittest/suite.py", line 122 in run File "/home/easybuild/Python-3.14.2/Lib/unittest/suite.py", line 84 in __call__ File "/home/easybuild/Python-3.14.2/Lib/unittest/suite.py", line 122 in run File "/home/easybuild/Python-3.14.2/Lib/unittest/suite.py", line 84 in __call__ File "/home/easybuild/Python-3.14.2/Lib/unittest/runner.py", line 257 in run File "/home/easybuild/Python-3.14.2/Lib/test/libregrtest/single.py", line 84 in _run_suite File "/home/easybuild/Python-3.14.2/Lib/test/libregrtest/single.py", line 42 in run_unittest File "/home/easybuild/Python-3.14.2/Lib/test/libregrtest/single.py", line 162 in test_func File "/home/easybuild/Python-3.14.2/Lib/test/libregrtest/single.py", line 118 in regrtest_runner File "/home/easybuild/Python-3.14.2/Lib/test/libregrtest/single.py", line 165 in _load_run_test File "/home/easybuild/Python-3.14.2/Lib/test/libregrtest/single.py", line 210 in _runtest_env_changed_exc File "/home/easybuild/Python-3.14.2/Lib/test/libregrtest/single.py", line 304 in _runtest File "/home/easybuild/Python-3.14.2/Lib/test/libregrtest/single.py", line 348 in run_single_test File "/home/easybuild/Python-3.14.2/Lib/test/libregrtest/main.py", line 393 in run_test File "/home/easybuild/Python-3.14.2/Lib/test/libregrtest/main.py", line 423 in run_tests_sequentially File "/home/easybuild/Python-3.14.2/Lib/test/libregrtest/main.py", line 563 in _run_tests File "/home/easybuild/Python-3.14.2/Lib/test/libregrtest/main.py", line 598 in run_tests File "/home/easybuild/Python-3.14.2/Lib/test/libregrtest/main.py", line 779 in main File "/home/easybuild/Python-3.14.2/Lib/test/libregrtest/main.py", line 787 in main File "/home/easybuild/Python-3.14.2/Lib/test/__main__.py", line 2 in <module> File "<frozen runpy>", line 88 in _run_code File "<frozen runpy>", line 198 in _run_module_as_main Current thread's C stack trace (most recent call first): Binary file "/home/easybuild/Python-3.14.2/libpython3.14.so.1.0", at _Py_DumpStack+0xa3 [0x155554c11883] Binary file "/home/easybuild/Python-3.14.2/libpython3.14.so.1.0", at +0x68adaa [0x155554c40daa] Binary file "/lib64/libpthread.so.0", at +0x12990 [0x1555543a8990] Binary file "/lib64/libc.so.6", at _IO_vfprintf+0x1b [0x15555389b44b] Binary file "/lib64/libc.so.6", at vsnprintf+0x94 [0x1555538c3aa4] Binary file "/home/easybuild/Python-3.14.2/libpython3.14.so.1.0", at PyOS_snprintf+0xea [0x155554bb058a] Binary file "/home/easybuild/Python-3.14.2/build/lib.linux-x86_64-3.14/_pickle.cpython-314-x86_64-linux-gnu.so", at +0x13084 [0x1555533a8084] Binary file "/home/easybuild/Python-3.14.2/build/lib.linux-x86_64-3.14/_pickle.cpython-314-x86_64-linux-gnu.so", at +0x1586f [0x1555533aa86f] Binary file "/home/easybuild/Python-3.14.2/build/lib.linux-x86_64-3.14/_pickle.cpython-314-x86_64-linux-gnu.so", at +0x1ba59 [0x1555533b0a59] Binary file "/home/easybuild/Python-3.14.2/build/lib.linux-x86_64-3.14/_pickle.cpython-314-x86_64-linux-gnu.so", at +0x15679 [0x1555533aa679] Binary file "/home/easybuild/Python-3.14.2/build/lib.linux-x86_64-3.14/_pickle.cpython-314-x86_64-linux-gnu.so", at +0x178f7 [0x1555533ac8f7] Binary file "/home/easybuild/Python-3.14.2/build/lib.linux-x86_64-3.14/_pickle.cpython-314-x86_64-linux-gnu.so", at +0x16820 [0x1555533ab820] Binary file "/home/easybuild/Python-3.14.2/build/lib.linux-x86_64-3.14/_pickle.cpython-314-x86_64-linux-gnu.so", at +0x1ba7c [0x1555533b0a7c] Binary file "/home/easybuild/Python-3.14.2/build/lib.linux-x86_64-3.14/_pickle.cpython-314-x86_64-linux-gnu.so", at +0x15679 [0x1555533aa679] Binary file "/home/easybuild/Python-3.14.2/build/lib.linux-x86_64-3.14/_pickle.cpython-314-x86_64-linux-gnu.so", at +0x178f7 [0x1555533ac8f7] Binary file "/home/easybuild/Python-3.14.2/build/lib.linux-x86_64-3.14/_pickle.cpython-314-x86_64-linux-gnu.so", at +0x16820 [0x1555533ab820] Binary file "/home/easybuild/Python-3.14.2/build/lib.linux-x86_64-3.14/_pickle.cpython-314-x86_64-linux-gnu.so", at +0x1ba7c [0x1555533b0a7c] Binary file "/home/easybuild/Python-3.14.2/build/lib.linux-x86_64-3.14/_pickle.cpython-314-x86_64-linux-gnu.so", at +0x15679 [0x1555533aa679] Binary file "/home/easybuild/Python-3.14.2/build/lib.linux-x86_64-3.14/_pickle.cpython-314-x86_64-linux-gnu.so", at +0x178f7 [0x1555533ac8f7] Binary file "/home/easybuild/Python-3.14.2/build/lib.linux-x86_64-3.14/_pickle.cpython-314-x86_64-linux-gnu.so", at +0x16820 [0x1555533ab820] Binary file "/home/easybuild/Python-3.14.2/build/lib.linux-x86_64-3.14/_pickle.cpython-314-x86_64-linux-gnu.so", at +0x1ba7c [0x1555533b0a7c] Binary file "/home/easybuild/Python-3.14.2/build/lib.linux-x86_64-3.14/_pickle.cpython-314-x86_64-linux-gnu.so", at +0x15679 [0x1555533aa679] Binary file "/home/easybuild/Python-3.14.2/build/lib.linux-x86_64-3.14/_pickle.cpython-314-x86_64-linux-gnu.so", at +0x178f7 [0x1555533ac8f7] Binary file "/home/easybuild/Python-3.14.2/build/lib.linux-x86_64-3.14/_pickle.cpython-314-x86_64-linux-gnu.so", at +0x16820 [0x1555533ab820] Binary file "/home/easybuild/Python-3.14.2/build/lib.linux-x86_64-3.14/_pickle.cpython-314-x86_64-linux-gnu.so", at +0x1ba7c [0x1555533b0a7c] Binary file "/home/easybuild/Python-3.14.2/build/lib.linux-x86_64-3.14/_pickle.cpython-314-x86_64-linux-gnu.so", at +0x15679 [0x1555533aa679] Binary file "/home/easybuild/Python-3.14.2/build/lib.linux-x86_64-3.14/_pnnickle.cpython-314-x86_64-linux-gnu.so", at +0x178f7 [0x1555533ac8f7] Binary file "/home/easybuild/Python-3.14.2/build/lib.linux-x86_64-3.14/_pickle.cpython-314-x86_64-linux-gnu.so", at +0x16820 [0x1555533ab820] Binary file "/home/easybuild/Python-3.14.2/build/lib.linux-x86_64-3.14/_pickle.cpython-314-x86_64-linux-gnu.so", at +0x1ba7c [0x1555533b0a7c] Binary file "/home/easybuild/Python-3.14.2/build/lib.linux-x86_64-3.14/_pickle.cpython-314-x86_64-linux-gnu.so", at +0x15679 [0x1555533aa679] Binary file "/home/easybuild/Python-3.14.2/build/lib.linux-x86_64-3.14/_pickle.cpython-314-x86_64-linux-gnu.so", at +0x178f7 [0x1555533ac8f7] Binary file "/home/easybuild/Python-3.14.2/build/lib.linux-x86_64-3.14/_pickle.cpython-314-x86_64-linux-gnu.so", at +0x16820 [0x1555533ab820] <truncated rest of calls> Extension modules: _testcapi, _testinternalcapi, _testlimitedcapi (total: 3) make: *** [Makefile:1004: profile-run-stamp] Segmentation fault [easybuild@login-rhel8 Python-3.14.2]$ I am at a bit of a lost here, any ideas what to try? Compiling with GCC 14.3 Let me know if you need addtional info. Kind regards Mads. This email is intended solely for the use of the individual or entity to whom it is addressed and it may contain confidential information. If It has been sent to you in error, please reply to notify the sender and delete this email from your system immediately. Grundfos takes your privacy seriously. If you want to know how Grundfos processes your personal data, please see our Privacy Policy.<https://www.grundfos.com/legal/privacy>

1 0

Handling large media downloads efficiently in Python (seeking guidance)
by oper max Dec. 9, 2025

Dec. 9, 2025

Hi everyone, I’m working on a small personal project to practice Python networking and file-handling techniques. The idea is to download media files from various publicly accessible URLs. For example, sometimes I test with short Instagram clips using an instagram downloader https://indown.io/en1 –style workflow, where the tool provides a direct media URL and I handle the download on my end. (Only for personal learning, not redistribution.) I’m mainly trying to understand: Best practices for streaming large files in Python without loading them fully into memory. Whether requests with streamed chunks is still the recommended approach, or if there are newer libraries/tools better suited for this. Safe ways to validate file types, avoid partial downloads, and handle connection drops. Any tips for structuring the code so the download logic stays clean and extensible. If anyone has suggestions, patterns, or examples from similar projects, I’d appreciate the guidance. Thanks!

1 0

Rock Paper Scissors Code Bug?
by yanovi＠uscstudents.org Dec. 9, 2025

Dec. 9, 2025

I coded Rock, Paper, Scissors. I added the randomness, made it loop at the user's request, added win code, no problems there. I changed some strings to F-strings to practice using them, and now the first "elif" in my if loop (player chooses rock, bot chooses paper) doesn't work. Any help ideas? I checked syntax, no error messages other than mine that I added Pasting code below the line: _____________________________________________________________________________ import random #Allows for a random input. options = ["Rock", "Paper", "Scissors"] #Tells the computer what its options are. playerchoices = [] repeat = True while repeat == True: rand_choice = random.randint(1,3) choice = options[rand_choice-1] #defines player options and selection while True: player_choice = input("Welcome to Rock, Paper, Scissors. To begin, choose Rock, Paper, or Scissors. ") if player_choice == "Rock": break if player_choice == "Paper": break if player_choice == "Scissors": break else: print("Invalid input, try again. Capitalize your response and ensure proper spelling. ") #Lines 10-19 give the player a choice as to what to pick. #The code below determines victory status. if player_choice == "Rock" and choice == options[0]: print(f"Computer played {options[0]}. Tie.") playerchoices.append("Rock") elif player_choice == "Rock " and choice == "Paper": print(f"Computer played {options[1]}. You lose.") playerchoices.append("Rock") elif player_choice == "Rock" and choice == options[2]: print(f"Computer played {options[2]}. You win.") playerchoices.append("Rock") elif player_choice == "Paper" and choice == options[0]: print(f"Computer played {options[0]}. You win.") playerchoices.append("Paper") elif player_choice == "Paper" and choice == options[1]: print(f"Computer played {options[1]}. Tie.") playerchoices.append("Paper") elif player_choice == "Paper" and choice == options[2]: print(f"Computer played {options[2]} . You lose.") playerchoices.append("Paper") elif player_choice == "Scissors" and choice == options[0]: print(f"Computer played {options[0]}. You lose.") playerchoices.append("Scissors") elif player_choice == "Scissors" and choice == options[1]: print(f"Computer played {options[1]}. You win.") playerchoices.append("Scissors") elif player_choice == "Scissors" and choice == options[2]: print(f"Computer played {options[2]}. Tie.") playerchoices.append("Scissors") else: print("If you're reading this, I messed up somehow") print(f"Choice: {choice}") print(f"You played: {player_choice}") playagain = True while playagain == True: ask_repeat = input("Play again? Y/N ") if ask_repeat == "Y": print("Restarting... ") repeat = True playagain = False elif ask_repeat == "N": repeat = False playagain = False print("Goodbye.") else: playagain = True repeat = False print("Error. Input either Y or N. Capitalize and retry.")

8 11

SQLObject 3.13.1
by Oleg Broytman Dec. 8, 2025

Dec. 8, 2025

Hello! I'm pleased to announce version 3.13.1, the first bugfix release of the branch 3.13 of SQLObject. What's new in SQLObject ======================= The contributors for this release are: * Igor Yudytskiy. Thanks for PR #194: fix: connect to old mssql versions via set tds_version uri parameter. * Dave Mulligan fixed #195: Minor ``NameError`` in ``pgconnection.py`` when using ``psycopg`` version 1 with a non-default port. Thanks! * Chris Kauffman found a minor bug in ``UuidValidator``. * GH user ghaushe-ampere. Thanks for finding an obscure bug! Bug fixes --------- * ``UuidValidator.from_python()`` now accepts strings as a valid input. This fixes #199. * Fixed #197: a bug in ``dbconnection.ConnectionURIOpener.registerConnection`` triggered by non-empty instance's ``name``. The bug was inserted in 2004 so it seems nobody ever used named instances. Fixed anyway. * Fixed #195: Minor ``NameError`` in ``pgconnection.py`` when using ``psycopg`` version 1 with a non-default port. Tests ----- * Tested with Python 3.14. * Run tests with source-only (non-binary) ``psycopg`` and ``psycopg2``. For a more complete list, please see the news: http://sqlobject.org/News.html What is SQLObject ================= SQLObject is a free and open-source (LGPL) Python object-relational mapper. Your database tables are described as classes, and rows are instances of those classes. SQLObject is meant to be easy to use and quick to get started with. SQLObject supports a number of backends: MySQL/MariaDB (with a number of DB API drivers: ``MySQLdb``, ``mysqlclient``, ``mysql-connector``, ``PyMySQL``, ``mariadb``), PostgreSQL (``psycopg``, ``psycopg2``, ``PyGreSQL``, partially ``pg8000``), SQLite (builtin ``sqlite3``); connections to other backends - Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB) - are less debugged). Python 2.7 or 3.4+ is required. Where is SQLObject ================== Site: http://sqlobject.org Download: https://pypi.org/project/SQLObject/3.13.1 News and changes: http://sqlobject.org/News.html StackOverflow: https://stackoverflow.com/questions/tagged/sqlobject Mailing lists: https://sourceforge.net/p/sqlobject/mailman/ Development: http://sqlobject.org/devel/ Developer Guide: http://sqlobject.org/DeveloperGuide.html Example ======= Install:: $ pip install sqlobject Create a simple class that wraps a table:: >>> from sqlobject import * >>> >>> sqlhub.processConnection = connectionForURI('sqlite:/:memory:') >>> >>> class Person(SQLObject): ... fname = StringCol() ... mi = StringCol(length=1, default=None) ... lname = StringCol() ... >>> Person.createTable() Use the object:: >>> p = Person(fname="John", lname="Doe") >>> p <Person 1 fname='John' mi=None lname='Doe'> >>> p.fname 'John' >>> p.mi = 'Q' >>> p2 = Person.get(1) >>> p2 <Person 1 fname='John' mi='Q' lname='Doe'> >>> p is p2 True Queries:: >>> p3 = Person.selectBy(lname="Doe")[0] >>> p3 <Person 1 fname='John' mi='Q' lname='Doe'> >>> pc = Person.select(Person.q.lname=="Doe").count() >>> pc 1 Oleg. -- Oleg Broytman https://phdru.name/ phd(a)phdru.name Programmers don't die, they just GOSUB without RETURN.

1 0

Re: A switch somewhere, or bug? CORRECTION
by Thomas Passin Dec. 8, 2025

Dec. 8, 2025

On 12/6/2025 6:49 PM, Em wrote: > For at least the last 10 years. I have been using double click on the > filename (or by shortcut) to use the program. It tracks the Insulin > injections for me and creates/updates several text files. I have been using > IDLE for editing on WIN10 computers. No issues.... > > When I copied the file to the new WIN11 computer and double-click on the > filename, it fails without warning or explanation. In WIN11, I can open the > file with IDLE and use F5 to run it successfully. > > I was told to try "Open with Python" and it fails on both the WIN10 and > WIN11 computers. I do not see the option for this program to Run as > Administrator on either computer. I have seen/used Run as Administrator > elsewhere on the WIN10 computer. > > I created a .py program with the lines of code: > > pause = input("Start") > Starter = open("HLY-LOG5.txt","w") > pause = input("End") > > and can follow all six of the techniques to run as mentioned above. Three > situations, the program runs, and three have the program fail. Exactly the > same results as with my medical program. > > Has my short, three line, program worked on your system? You should have sent this message to the group, not just me. Yes, your program created the file but not when I double-clicked on the file name. As I explained in my last post, that's because in Windows 11 when double-clicking, the working directory is the system's Windows directory, not the one your program is in. In Win 11, you don't have access to it as an ordinary user. Anyway even if you did, you don't want to write your file there. There's a simple solution if you want to be able to launch by double clicking the file. Actually, there are at least four ways to go. 1. Run your program using a batch file. in the batch file, cd to your target directory before launching your program. The batch file needs to be somewhere on your path, or alternatively you can put a shortcut to it on your desktop. If you don't know how to do any of those things, ask for help. 2. Make your Python program change directories to the target directory before writing the file. I think someone already posted a code snippet showing how to do that. If not, and you don't know how, ask for help. 3. Hard-code the full path to your target file. Then it won't matter what working directory is in effect. 4.Create a shortcut for your .py file on the desktop. Then open the Properties dialog for the shortcut. In the "Shortcut" tab you can put the desired working directory. Now when you double click the shortcut, it will open in the right directory. > -----Original Message----- > From: Thomas Passin <list1(a)tompassin.net> > Sent: Saturday, December 6, 2025 4:17 PM > To: python-list(a)python.org > Subject: Re: A switch somewhere, or bug? CORRECTION > > On 12/6/2025 2:51 PM, Em wrote: >> >> The confusing part here is that no one has indicated whether or not >> the statement fails in any of the six ways to run this program except me. >> >> Am I the only one that as the problem? > > No. I created the program with the suggested printout of the working > directory. Here's what I ran: > > import os > print("Start") > print("working directory:", os.getcwd()) > input(" Starter file") > > try: > Starter = open("HLY-LOG5.txt","w") > except Exception as e: > print(f"Error: {e}") > input("End") > > It ran but failed to create the file. That's because of the working > directory when the program was run by double-clicking its name. Here's the > output. > > Start > working directory: C:\WINDOWS\system32 > Starter file > Error: [Errno 13] Permission denied: 'HLY-LOG5.txt' > End > > An ordinary user doesn't have permission for the C:\WINDOWS\system32 > directory. Maybe on your Windows 10 system the working directory was the > program's directory. But with the new file association system it's not. I > think it should be, myself. > > When I ran the program by typing just its name in a terminal opened on the > program's directory, it created the file without any errors. > > I'm running Python 3.12+, but the exact version won't matter because the > initial working directory is set by Windows, not Python. > > If you really really want programs that reliably write to the program's > directory, you can get it from sys.argv[0] and have Python change > directories for you. Otherwise, start your program in some other way than by > double-clicking. > >> -----Original Message----- >> From: Peter J. Holzer <hjp-python(a)hjp.at> >> Sent: Saturday, December 6, 2025 12:56 PM >> To: python-list(a)python.org >> Subject: Re: A switch somewhere, or bug? CORRECTION >> >> On 2025-12-04 18:03:34 -0500, Em wrote: >> ^^^^^^^^^^ >> Weird. That was before most of the thread (and the message wasn't >> stuck in a moderation queue), yet it seems everybody ignored this message. > . >> Probably because it isn't actually part of the thread, but ... >> >>> On my computer: Win11, Python 3.14.1 >>> >>> >>> >>> Double-click and run on the file". You will see the first two lines >>> execute. >>> >>> The screen will show "Start" and "Starter File". >> >> Good. So we know that the program is executed. >> >>> Hit <Enter> to resolve the >>> pause statement and the program crashes when it tries to create the >>> "HLY-LOG5" file. The last line, "End" is not printed. No file is created. >> >> So the next step is to find out why it isn't executed. First print the >> working directory: >> >> import os >> print("Start") >> print("working directory:", os.getcwd()) >> input(" Starter file") >> >> then wrap the open in a try/except block: >> >> try: >> Starter = open("HLY-LOG5.txt","w") except Exception as e: >> print("Error: {e}") >> input("End") >> >> This should now tell you in which directory the program is actually >> trying to create the file and why it didn't work. >> >> hip >> > > -- > https://mail.python.org/mailman3//lists/python-list.python.org >

6 12

What is the tool used here?
by Em Dec. 7, 2025

Dec. 7, 2025

I see >, >>, and >>>, attached at the beginning of lines in messages. I doubt that they are placed manually and wonder how they are placed automatically. How do I get said program? ============================ A voice mail message recently left on my phone: "Please call us back at: 16 billion 863 million 431 thousand and 125"

5 6

RE: Re: A switch somewhere, or bug? CORRECTION
by Em Dec. 7, 2025

Dec. 7, 2025

No changes. Run the file is the folder or run it using IDLE. Copy the same file to the WIN10 Python 3.13 and both situations run as expected. Maybe the attached file might explain. No BSOD. Permissions don't change. I tried to send a file as an attachment, failed/rejected as spam. Here it is as text. #=================================================================== """ On my computer: Win11, Python 3.14.1 Double-click and run on the file". You will see the first two lines execute. The screen will show "Start" and "Starter File". Hit <Enter> to resolve the pause statement and the program crashes when it tries to create the "HLY-LOG5" file. The last line, "End" is not printed. No file is created. Press F5 to activate the program here in IDLE. The program executes properly and the empty file "HLY-LOG5" text file is created. Why did it crash with the double-click? """ print ("Start") pause = input(" Starter file") Starter = open("HLY-LOG5.txt","w") pause = input("End") #====================================== Curious, will there be a version 3.14.15926? ============================ A voice mail message recently left on my phone: "Please call us back at: 16 billion 863 million 431 thousand and 125"

4 5