r/PythonProjects2

There are some interesting patterns in the data and a few results I definitely did not expect. I have put the analysis and visualizations together here. Have a look and let me know what you think or if there is anything you would approach differently.

I thought it would be interesting to see what everyone here is actually building with Python.

If you're working on a project, share it below or in r/PythonBuilders . It can be anything — an app, game, automation tool, library, SaaS, API, desktop app, or even a small experiment.

If you can, tell us:

• What are you building?
• What does it do?
• How far along are you?
• What's the biggest challenge you're dealing with right now?

It doesn't have to be finished or impressive. I'm more interested in seeing what people are working through and learning along the way.

What are you building?

So basically, I’m taking a python course, and my last session will be in two weeks, and I need to make a « final project », and I’d like to get some suggestions please 🙏🏻

Implementing network-based multiplayer games is a challenge. At the same time, game development has always been a popular choice among beginners.

For this reason I have developed a lightweight server and framework for turn-based multiplayer games. It was primarily designed for a programming course where students work on projects in small groups. However, the use of the server is not limited to educational scenarios.

• Implementing clients is easy thanks to a user-friendly API.
• Adding new games is accomplished by deriving from a base class and overriding its methods.

Here is a short demo of the API usage:

from game_server_api import GameServerAPI, IllegalMove

game = GameServerAPI(server='127.0.0.1', port=4711,
                     game='Yahtzee', session='mygame', players=3)

my_id = game.join()   # start/join a session
state = game.state()  # returns a dictionary

while not state['gameover']:
    # print game board here

    if my_id in state['current']: # my turn
        pos = None
        # read user input here

        try:
            game.move(position=pos) # perform a move (**kwargs)
        except IllegalMove as e:
            # something went wrong
    else:
        # opponent's turn

    state = game.state()

# end of game

It's open source: https://github.com/feberts/python-game-server

I built a free J.A.R.V.I.S. OS web app using Streamlit & Groq. Would love your feedback on speed & UI!

If you are learning Python through projects, I think a file organizer is a really good project to build early.

It is simple enough that you can get a working version without knowing advanced Python, but it also introduces the kind of problems that make a small script feel like actual automation rather than another syntax exercise.

The idea is straightforward.

Your Downloads folder probably looks something like this after a while:

resume.pdf
photo.png
expenses.csv
backup.zip
notes.txt
video.mp4

The script should look through those files and organize them automatically.

You might end up with:

Documents/
    resume.pdf
    notes.txt

Images/
    photo.png

Data/
    expenses.csv

Archives/
    backup.zip

Videos/
    video.mp4

The first version does not need to be complicated.

I would start by using pathlib to find the folder and inspect the files inside it.

from pathlib import Path

downloads = Path.home() / "Downloads"

for file in downloads.iterdir():
    if file.is_file():
        print(file.name)

That already gives you a useful starting point.

Now the program needs to decide what each file actually is.

One simple way is to create categories based on file extensions.

FILE_TYPES = {
    "Images": [".png", ".jpg", ".jpeg"],
    "Documents": [".pdf", ".txt", ".docx"],
    "Data": [".csv", ".json", ".xlsx"],
    "Archives": [".zip", ".rar"],
    "Videos": [".mp4", ".mov"]
}

Then get the extension of each file with:

extension = file.suffix.lower()

From there, you can compare the extension with your categories and decide where the file should go.

But I would not let the script move anything yet.

Make it print its decision first.

resume.pdf -> Documents
photo.png -> Images
expenses.csv -> Data
backup.zip -> Archives

I think this is one of the most useful habits you can learn from a small automation project.

Before your code changes real files, make sure you understand what it is about to do.

Once the classification logic works properly, you can create the destination folder if it does not already exist.

destination = downloads / category
destination.mkdir(exist_ok=True)

Then you can move the file.

For a simple version, Python's standard library gives you several ways to handle this. I would probably use shutil.move() once the project starts moving real files.

import shutil

shutil.move(str(file), str(destination / file.name))

At this point, you technically have a working file organizer.

But this is also where the project starts getting interesting.

Imagine Documents already contains a file called resume.pdf.

Should your script overwrite it?

Rename the new one?

Skip it?

Ask the user?

There is no single correct answer, but now you are making an actual software decision instead of following a tutorial.

The same thing happens with unknown file types.

Maybe somebody downloads a .psd file and you never created a category for it. You could ignore it, put it inside an Others folder, or allow the categories to be configured separately.

Then there is the biggest risk with this kind of project: accidentally moving files you did not intend to move.

That is why one of the first improvements I would add is a dry-run mode.

Instead of immediately changing the folder, the script could show:

Would move resume.pdf -> Documents/
Would move photo.png -> Images/
Would move backup.zip -> Archives/

You review the result first, and only then allow the program to perform the moves.

Once that works, add logging. Record what was moved, where it came from, and where it went. Now you have enough information to eventually build an undo feature. That progression is what makes this a good beginner project. The first version teaches loops, dictionaries, conditions, file extensions and pathlib. The next version teaches file operations and folder creation. Then duplicate handling introduces edge cases. Dry-run mode introduces safer automation. Logging introduces observability. Undo support forces you to think about reversibility. You can start with 20 or 30 lines of Python and keep improving the same project as your skills improve.

I would build it roughly like this:

Version 1: Read the files and print their extensions.

Version 2: Classify each file into a category.

Version 3: Print where each file would be moved.

Version 4: Move the files.

Version 5: Handle duplicates and unknown extensions.

Version 6: Add dry-run mode and logging.

Version 7: Add undo support or turn it into a small CLI tool.

The important part is not building all seven versions immediately.

Build the smallest version first. Then use the problems you encounter to decide what to learn next. That is usually where a beginner project becomes much more useful than simply copying a finished script.

If you built this, what would you add after the basic file organizer worked?

https://preview.redd.it/oztx9xxqqiih1.png?width=1726&format=png&auto=webp&s=93b10e75cc32956dab566747e10e0d4493b60281

Hi everyone,

I'm a 15-year-old student from Morocco who's been learning Python and cybersecurity over the past year.

While experimenting in an authorized environment, I discovered that traditional tools such as Hydra couldn't interact with a Dahua DVR's JavaScript-based login page. Instead of giving up, I decided to build my own Python framework using Selenium to automate browser-driven authentication testing.

The project is called RedaForce.

GitHub: https://github\\\[.\\\]com/REDA-MAH/RedaForce

I'm not posting this to ask for stars. I'd genuinely appreciate technical feedback on:

Code quality and project structure

README and documentation

Python best practices

Repository organization

Features you think would make the project more useful

I'm still learning, so I'm especially interested in constructive criticism from more experienced developers.

Thanks for taking the time to look!