# Hello-Python is three directories and a paused course, with one dead deployment target > mouredev's Hello-Python is a Spanish-language Python course of 100 classes delivered as long YouTube videos, with code kept in three directories. Two advertised projects live in other repositories, the frontend material is not in this one at all, and the backend track deploys to a service that no longer exists. **mouredev/Hello-Python** — Curso para aprender el lenguaje de programación Python desde cero y para principiantes. 100 clases, 44 horas en vídeo, código, proyectos y grupo de chat. Fundamentos, frontend, backend, testing, IA... - Repository: https://github.com/mouredev/Hello-Python - Website: https://mouredev.link/python - Stars: 37,619 · Forks: 2,343 - Language: Python - License: Apache-2.0 - Published: 2026-08-17 · Updated: 2026-08-18 · Language: en - Canonical page: https://hysenlabs.com/projects/mouredev-hello-python ## The entire code base is three directories and no environment file The top-level entries are .gitignore, Backend/, Basic/, Images/, Intermediate/, LICENSE, and README.md. That is the whole project. There is no requirements file at the root, no pyproject.toml, no package manifest, no test runner, and no GitHub release, so there is nothing to install and nothing to pin. Each of the three course blocks names its directory explicitly, Basic for the fundamentals, Intermediate for the second fundamentals course, and Backend for the API track, which means the mapping from a lesson to a file is something you work out yourself by reading the code. The single requirements file the project points at lives inside the backend track, at Backend/FastAPI/requirements.txt, and it exists so a deployment platform can build that one service. Nothing sets up an environment for the Basic or Intermediate material, so the version of Python you learn against is whichever one your machine already has. ## The frontend projects and the AI examples are not in this repository The README advertises a frontend track with two real projects deployed in production and about nine hours of step-by-step video, and the code for both is linked out rather than included. One points at a separate python-web repository and the other at a separate adeviento-web repository. Clone this one and you get no frontend code at all. The same pattern shows up in the standalone sessions: the one-hour class on integrating ChatGPT into a project, covering conversation handling and setting the AI context, publishes its code to a GitHub gist, and the voice translator class, which claims to build a multilingual translator in a hundred lines, does the same. So four pieces of advertised material live somewhere other than the repository you are reading. Gists in particular carry no changelog and no version tag, so if you build on the ChatGPT example you have no way to tell which revision you copied. ## Backend lesson 18 deploys to Deta, and Deta no longer exists The backend track runs for eighteen lessons and ends with deployment. The lesson is titled deployment on Deta, and there is a correction note attached to it saying that Deta, the service used for the deployment during the course, no longer exists. The replacement advice is concrete: read the official FastAPI documentation on deployment, use one of the free providers FastAPI recommends, and, in the author's case, two files are left in the tree for it, a configuration file at Backend/FastAPI/vercel.json and a dependency file at Backend/FastAPI/requirements.txt, with the instruction to select the Backend/FastAPI directory as the project root on Vercel. That is a genuinely useful note and it is the only one like it in the project. It also means the final lesson of the longest track has no runnable target, so a learner working through the course in order hits a wall at the end and has to make a hosting decision that the video never walks them through. ## The basic course is one video longer than ten hours Each track is a single YouTube video with a list of chapters, and the only index is a set of timestamps. The fundamentals video runs from an introduction and a context section through fifteen lessons covering setup, hello world, variables, operators, strings, lists, tuples, sets, dictionaries, conditionals, loops, functions, classes, exceptions, and modules, and then a closing next-steps section. The last of those timestamps is at 36,390 seconds, which puts the single video past ten hours. The intermediate track is one video of at least 26,228 seconds, and the backend one at least 28,484 seconds. The consequence is that you cannot jump to a lesson the way you would in a course with one file per topic. You scrub a ten-hour video to a timestamp, and if the timestamps drift because a video is ever re-uploaded, the index silently stops matching. There is no table of contents file in the repository to regenerate from. ## The project says it is paused, and the last push was 2025-08-11 There is a section of important information and frequently asked questions, and it opens by stating that the course is currently paused. The basic, intermediate, and backend blocks are finished, and that was the original goal of the project. New lessons are not ruled out for the future, but nothing is scheduled. The dates line up with that. The last push to the default branch is 2025-08-11, more than a year before now, and the repository publishes no GitHub releases, so there is no version history to consult and no signal that anything landed since. For a course this is a reasonable place to stop. For code it means the Basic and Intermediate material has had no attention in that window, and if you are evaluating the examples as patterns to copy rather than as lessons to watch, you are reading code that has not been touched in over a year. ## The backend track has no testing and no production database lesson Read the eighteen backend chapter titles in order and the shape of the track is clear. It opens by asking what a backend is, moves into API and FastAPI, adds type hints and FastAPI configuration, then a hello world, a GET operation, HTTP requests, API creation, path and query parameters, POST, PUT and DELETE operations, HTTP status codes, routers, static resources, OAuth2 authorisation, OAuth2 with JWT, MongoDB, and MongoDB Atlas. Every chapter is about serving a request. None of them is about writing tests, none is about migrations or schema management, and none covers anything past a hosted free tier of MongoDB Atlas. Testing exists in the project as a separate workshop, an introduction created with two named collaborators, rather than as a chapter inside the track, so the testing content is standalone rather than integrated with what the backend code teaches. The result is a complete first API and no guidance on keeping it correct as it grows. ## Reflex is badged at the top, and no Reflex code is in the tree The badge row at the top of the file links Python itself, the FastAPI documentation, MongoDB, the OpenAI platform, and Reflex. The top-level entries of the repository are .gitignore, Backend/, Basic/, Images/, Intermediate/, LICENSE, and README.md. Nowhere in that list is a Reflex project, and the frontend section sends you to two different repositories for the web material instead. The badge row is a link bar rather than an inventory of what the code uses, and reading it as a stack summary will mislead you about what is actually here. The same applies to the OpenAI platform link: the only OpenAI material in the project is that single one-hour class whose code is in a gist, not in this tree. If you are scanning badges to decide what a repository teaches, this one will overstate its coverage by a wide margin. ## Everything here is in Spanish, and the chat group is off-repository The whole project is written and taught in Spanish. The description, the course descriptions, every chapter title, and the deployment correction are in that language, and there is no English version of the README in the top-level entries. The code is of course unaffected, so a reader who does not read Spanish gets working code for three tracks and no explanation of why any line is the way it is, which is most of the value of a fundamentals course. The description also advertises a chat group alongside the hundred classes, forty-four hours of video, and the projects. That group is not a repository artefact, so nothing in the files tells you whether it is active, what its rules are, or whether the other participants are still there. The community part of the pitch is the one piece of the project you cannot inspect before deciding to join it. ## Conclusion Hello-Python suits a reader of Spanish who wants one continuous path from variables and collections through FastAPI, OAuth2 with JWT, and MongoDB Atlas, and who is willing to scrub ten-hour videos rather than jump to five-minute lessons. It is a course rather than a reference, and it is finished rather than ongoing: the project states that it is paused, and the last push to main is dated 2025-08-11. Before starting the backend track, know that lesson 18 deploys to Deta, which no longer exists, and that the frontend projects and the AI example code are not in this repository at all. ## FAQ ### How do I say hello in Python? The Hello-Python basics track covers exactly that in Leccion 2 - Hola Mundo, the second chapter of the fundamentals video, listed at the 1518 second timestamp. The code for that track is kept in the Basic directory of this repository, so the file is there even though the explanation is in Spanish. ### What is greet() in Python? No greet() function is defined anywhere in the three course directories of this repository. The hello world material the project does cover is Leccion 2 - Hola Mundo in the fundamentals track, and its code lives in the Basic directory. ### What does the mouredev Hello-Python repository contain? The top-level entries are .gitignore, Backend/, Basic/, Images/, Intermediate/, LICENSE, and README.md, with the three directories holding the code for the fundamentals, intermediate, and backend tracks. There is no requirements file at the root and no GitHub release, and the project is MIT-style permissive under Apache 2.0. The last push to main is dated 2025-08-11. ### Can I follow the Hello-Python backend course today? Yes for everything except the final deployment chapter. The lesson uses Deta, and a correction note in the README states that Deta no longer exists. The replacement is FastAPI's own deployment documentation and its list of free providers, plus a vercel.json and a requirements.txt under Backend/FastAPI, to be deployed from Vercel with that directory as the project root. ## Sources - [Official documentation](https://mouredev.link/python) - [Official README](https://github.com/mouredev/Hello-Python#readme) - [Project repository](https://github.com/mouredev/Hello-Python) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/mouredev-hello-python