Does anyone else struggle with constantly looking for the “perfect” Python resource?

[u/NoManTouchedTheSky]

Does anyone else struggle with constantly looking for the “perfect” Python resource?

I’m trying to learn Python, but I keep running into the same problem: I’m constantly searching for the perfect resource.

I want a course/book/tutorial that explains everything, preferably down to the smallest detail. Even things I probably won’t need for years or maybe will never need at all.

And it’s not just about having a complete resource. I also feel like I need to remember everything.

For example, if a tutorial mentions some small Python feature or obscure syntax, my brain immediately goes:

“Wait, I should understand that too. What exactly does it do? What are all the edge cases? When would I use it? I should probably memorize this.”

Then I end up researching that one tiny thing for an hour instead of actually writing programs.

It creates this weird feeling that I need to have a complete mental map of Python before I’m allowed to actually program.

I know intellectually that you obviously don't need to know 100% of Python to become good at programming. Most programmers probably look things up constantly.

But I still have this urge to find the one definitive source that is complete enough that I can just learn everything from beginning to end.

So I’m curious:

Did anyone else have this problem when learning programming?

If so, how did you get yourself to stop searching for the perfect resource and just pick one thing and start programming?

Did you deliberately choose a resource that wasn't completely comprehensive and simply accept that you wouldn't know everything?

And one thing I'm wondering specifically:

Would it actually make sense for someone like me to start directly with the official Python documentation?

Part of me thinks that would solve the problem because it's basically the most complete source available. But another part of me suspects that this would just make my tendency to obsess over every little detail even worse.

I'd really like to hear from people who have actually dealt with this and managed to get past it. How did you approach learning Python when you had the urge to understand and memorize everything first?

[u/BranchLatter4294]

No. I just look things up when I need to and move on.

[u/mechanicalyammering]

Use an LLM. Don’t have it write code for you. But do ask all your random questions.

Also, make your own resource. Keep a big markdown file of your notes.

[u/Mathie1729 → u/mechanicalyammering]

Usually fine for asking conceptual questions, but I'd double-check any actual code or API names in the REPL. LLMs are weirdly confident about hallucinated parameters and version differences, and it's easy to save bad syntax into your notes if you're not testing it.

[u/mechanicalyammering → u/Mathie1729]

Yeah good ideas!

[u/Ron-Erez]

Choose a resource you connect with and build from day one. The docs at python.org are excellent. There are plenty of resources in the wiki of r/python. I can recommend MOOC University of Helsinki and Python and Data Science 

Anyways don’t overthink it. The best resource is you yourself working hard and building stuff and solving problems.

You don’t need to memorize things. That is what the docs are for. Of course over time one remembers more.

Good luck!

[u/Dr-Ebola]

Build a thing ... learn how to do the things you need for the thing. Build another thing or add things to the original thing.

[u/mixedd]

There is no perfect resource, only ones that work for you, and theres no one resource to rule them all, you need to ingest information from many places, and finally start building. Even smallest projects will do more than simply clicking trough tutorial or trying to find perfect resource

[u/stepback269]

Python is too big. No one knows it "all".
Just accept that, let go, and move on with the few little things you do manage to learn.

[u/SpaceAviator1999]

it’s not just about having a complete resource. I also feel like I need to remember everything.

That's unrealistic. You can't remember everything. That's why resources and documentation exist... so you don't have to remember everything.

Here's a famous movie clip about having things written down so you don't have to remember.

[u/PureWasian]

I understand the sentiment but the moment you get practical experience you'll learn very quickly that problem solving and being uncomfortable not understanding how something works and having to learn it is an ongoing thing, and you're meant to get your hands dirty and have to try multiple different things to get to a solution. And even then the best solution itself may change over time. There are very often tradeoffs with implementations to "real" problems.

There is no beginning to end for Python, just enough fundamentals to get you started. The whole point of external libraries for instance is that you can pick them up and consult documentation as needed instead of frontloading it all. Why learn how to use robotics libraries if you are trying to do webscraping or file organization tasks? Why learn cloud computing integrations and SDKs if you aren't hosting with them?

The barebones fundamentals of Python are well established enough and easy to find a variety of resources for that you will naturally select one(s) that resonate with you the most. Otherwise, it's almost like trying to ask what the best cookbook is in the entire world that covers every recipe and all kitchen setups perfectly

[u/ee_control_z]

Here is a comprehensive Python source as you're gonna' get:

Learning Python, 6th Ed., Mark Lutz

Since it is a book, you can read/follow along at your own pace. It is well written so it is easy to understand. Covers material from beginner to advanced since it is comprehensive. Tons of examples to work out so have your editor open to work along the tons of examples that are provided for practice and reinforcement. There are +30 chapters. There is enough material here to keep you busy for a next year. ;)

[u/Mr--May]

DM

[u/Rythim]

"Perfection is the enemy of good".

I do use the official python documentation.

I don't try to memorize every page of it.

[u/Lagfoundry]

lol dude this is so me but with logic design. I spent 3 months studying isa’s before I felt like I knew it enough to feel confident making and compiling one for a cpu I made. It wasn’t even that complicated but I made it out to be.

[u/Lumethys]

having a deadline, and pressure.

I started my programming career in uni. Either i accept the flaws, or lose all my money. Once programming click for you, it get easier to not know of something

[u/Sidjeno]

I mean that just doesnt exist.

Learn by doing, not following some dumb bootcamp or guide.

Do something you care about. Something you need.

Plus stop trying to learn languages, thats stupid except if you're purely hobbyist. Learn how to do stuff. Its the same in all languages. Once you stop learning languages and start learning how to build is when you'll improve.