Skip to main content

File Writing , Temporary Memory , Creating A New File , Close , Preventing Overwrite , New Lines

 


File Writing 

Our repls don't need to be just one file that contains all of the code and data. We can write data to other files for longer term storage, then access it when we need it. 

To do this we're going to use the Files tab in the left hand toolbar. It looks like this 

 


Temporary Memory

When we use variables, lists, dictionaries and other data structures in our code, the data inside them are stored in the computer's RAM.
RAM is temporary storage (usually called memory). It's used to hold data and instructions for programs that your computer currently has open.
The problem is, that when a program finishes, or is closed, its data and instructions are removed from the RAM to free up space.
This is why you had to re-input all of your test data for your dynamic list & dictionary programs every time you ran them. The contents of those lists/dictionaries were removed from RAM when the program finished executing.



Creating A New File

To avoid this incredibly annoying data re-entry task, we are going to get the program to save data into a file. The file will exist in secondary storage (the hard drives on Replit's servers in this case).
πŸ‘‰ Here's how to open a file. This one line of code has three important features: 


 
f = open("savedFile.txt", "w") 

The variable (f): This is needed to allow your program to communicate to the file. Normally this would have a lovely meaningful name. However, you will need to type this variable name lots, and lots, and lots. So short is good. 'f' is short for 'file'.


The file name (the first item in brackets, "savedFile.txt"): You MUST code this to match the filename EXACTLY and include the file extension.


The 'w' (second item in brackets): This sets the permissions for the file. 'w' means 'write'. This means that if the file doesn't already exist, the program will create a new blank file with that file name. However, if it does already exist it will be overwritten with a blank file.

Save Me! Writing Data To The File 


πŸ‘‰ The .write() command will write the piece of data in brackets into the file. You can use as many of these as you want.


 
f = open("savedFile.txt", "w")
f.write("Hello there")

Close


πŸ‘‰ However, this data IS STILL IN THE RAM. Nothing gets saved until we close the file using the .close() command.


f = open("savedFile.txt", "w")
f.write("Hello there")
f.close()



When you run this code, nothing will appear in the console, but check the files tab on the left.
Gasp! A file has been created. 



Click on it to view the contents! 





 

Saving to Files

πŸ‘‰ Now let's get some input, store it in a variable, and write it to the file.


f = open("savedFile.txt", "w")
whatText = input("> ")
f.write(whatText)
f.close()

Preventing Overwrite


We're going to change the file permissions from 'w' to 'a+'.
'a' means append - add to the end of the file.
However, if the file doen't exist, then it will crash.
'a+' means 'add to the end of the file, or create a new one if it doesn't exist'.
πŸ‘‰ Here's the amended code with the change on line 1:

f = open("savedFile.txt", "a+")
whatText = input("> ")
f.write(whatText)
f.close()

The problem with this is that it just glues the second input straight on to the first. Like this: 

New Lines

πŸ‘‰ We can use our old friend, the fString, to format a new line. I've used the \n new line character.

f = open("savedFile.txt", "a+")
whatText = input("> ")
f.write(f"{whatText}\n")
f.close()


 

f = open("savedFile.txt", "a+")
whatText = input("> ")
f.write(f"{whatText}\n")
f.close()


Comments

Popular posts from this blog

Automate! Automate!

 Making this customizable πŸ‘‰So how about making our search user customizable? In the code below, I have: Asked the user to input an artist (line 14) Tidied up their input (line 15) formatted the search URL as an fString that includes the artist (line 19) Here's tAutomate! Automate! We are so close. I can taste it, folks! Massive kudos on getting this far! Today's lesson, however, will work best if you have one of Replit's paid for features (hacker plan or cycles). Free plan Repls 'fall asleep' after a while. Automation kinda relies on the Repl being always on. If you have hacker plan or you've bought some cycles, then you can enable always on in the drop down menu that appears when you click your Repl name (top left).he code: This is important because when our repl is always running, it can keep track of time and schedule events. πŸ‘‰ I've set up a simple schedule that prints out a clock emoji every couple of seconds. It works like this: Import schedule librar...

HTTP & Sessions

 HTTP & Sessions One of the main protocols (rules that govern how computers communicate) on the web is called HTTP. HTTP is what is known as a stateless protocol. This means that it doesn't 'remember' things. It's a bit like having a conversation with a goldfish. You can ask a question and get a reply, but when you ask a follow up question, the original has already been forgotten, as has who you are and what you were talking about. So if HTTP is stateless, how come my news site remembers to give me the weather for my home town, my preferred South American river based online store tells me when it's time to order more multivitamins, and I'm justifiably proud of my #100days success streak? The answer is......... Sessions Sessions are a way of storing files on your computer that allows a website to keep a record of previous 'conversations' and 'questions' you've asked. By using sessions, we can store this info about the user to access later....

Incoming!

 Incoming! Today, we're going to learn how to deal with data from forms in Flask. πŸ‘‰ To start, I've added yesterday's HTML code for my form in main.py for you already. (You're welcome!) Go take a look! πŸ‘‰ However, at the moment, the app.route() has no method associated with it, so I need to create a route for this page to receive the data. First, I need a new import: request. Then I create the app.route - I also need to add an extra argument to specify the methods being received. At the moment, that's just 'post', but it does need to be ALL CAPS - POST. Finally I define the process() subroutine that returns request.form πŸ‘‰ Here's the new code on its own: from Flask import Flask, request app.route('/process', methods=["POST"]) def process():   return request.form πŸ‘‰ And here it is as part of the whole code: from flask import Flask, request app = Flask(__name__) app.route("/process", methods=["POST"]) def process():   ...