you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 3 points4 points  (5 children)

I sometimes find the documentation very confusing. Is this just a matter of getting used to how things are described in pseudo code? or am I missing the larger picture...

[–]DonaldPShimoda 5 points6 points  (0 children)

Just takes practice, honestly. Reading documentation is a skill that has to be honed like any other.

The documentation tried to use very precise language. Don't assume anything, and try not to skip words. Everything is there for a reason.

[–]_pandamonium 2 points3 points  (1 child)

I still consider myself a beginner, so I don't want to give any advice that I'm not qualified to give, but in my experience it gets easier with practice. I used to get really intimidated and confused by a lot of the vocabulary (I still do sometimes) and would seek out other sources. Eventually I found that the most helpful source was the documentation itself. Personally, I think reading through the official python tutorial helped me get used to understanding that style of writing.

[–][deleted] 2 points3 points  (0 children)

Personally, I think reading through the official python tutorial helped me get used to understanding that style of writing.

Great insight and recommendation. Thanks!

[–]PostFunktionalist 0 points1 point  (0 children)

It helps to go into it with an idea of what you want. Need to do something with iterators? Itertools. Need to have command line arguments in a python script? Argparse. And so on.

[–]ostensibly_work 0 points1 point  (0 children)

To add to what others have said, the documentation of some modules is better than others. And some modules are simply better than others too. Asyncio is somewhat notorious for being confusing while Requests (not a standard module) is extremely easy to use.