Run your first Python program
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 55/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- git, python
- Domain
- documentation
Research direction
Open get-quote.py and inspect line 2, then run it with Python 3 using the command shown in the issue. Confirm that the hard-coded quote appears in the terminal, check git status, and follow the documented add, commit, and push steps so the file change is recorded.
Written by the indexing model from the issue text.
Description
Now you're ready to start coding. Let's get familiar with the files in our repo:
README.md: a markdown introduction to this projectget-quote.py: the file where we'll write our Python codequotes.txt: a text file with a list of quotes
Open up get-quote.py and comment out line 2 by removing the # from the beginning of the line. It will look like this:
print("Keep it logically awesome.")
The two spaces (or one tab) in front of the line is important. Python uses whitespace to organize code. This print line is part of the main() function. But more on that in the next step. First, let's try running that Python script.
Use the Python 3 command to run the script. From the command line, type one of the following:
python get-quote.pypython3 get-quote.py
You should see our first quote, the one hard-coded into line 2, printed out in your terminal:
Keep it logically awesome.
Push your changes
You've edited your local code, so you have a more recent version than is stored in this repository. You can check that any time by running: git status
It should show one file modified. Every time we want to send our local changes to GitHub, we need to perform three steps:
- Add the file(s) with changes:
git add get-quote.py - Commit the changes:
git commit -m "Hello World" - Push the changes:
git push
Once you've completed these steps, we'll write some more Python.
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
essnmx good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
[Feature] 奇物选择添加优先级 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Giskard-AI/giskard-oss#2840 · 1 comment ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Openarea: repo bug perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yeti-platform/yeti#1380 ·