On Sun, Apr 28, 2019 at 03:00:12PM +1000, Nathan D'Elboux wrote:

> this is a learning exercise for me so how do more experienced python coders
> approach modules like this, when you encounter a module that has sparse
> documentation how do you learn more about the functionality of said module?
> 
> unpack it and just read the source?

If there's no documentation, read the source. If the documentation is 
inaccurate, incomplete or poor, read the source. If the source code is 
hard to read and understand, cry.

> or is there like a linux man page
> equivalent within the wheel that would provide more context?

Wheels don't magically create documentation out of thin air. If the 
library isn't documented, where would it get the documentation from?



-- 
Steven
_______________________________________________
Tutor maillist  -  Tutor@python.org
To unsubscribe or change subscription options:
https://mail.python.org/mailman/listinfo/tutor

Reply via email to