In python the readability come as a natural idiom, it is part of their zen!Superficial readability, perhaps.
Neither PEP 8 nor PEP 20 get into interesting questions about maintainability like:
* How long should individual compilation units be?
* How do I factor my code?
* What metaphors do I use to name components?
* How do I know when to break apart components?
* How do I know when to merge components?
* How do I write effective documentation?
* Is this API easy to use?
* Have I sufficiently encapsulated this component?
* How easy is this code to test?
* Does this code match local style?
* Does this code follow the idioms and express the necessary elements of the problem domain effectively?
* Is it easy to misuse this API?
* Have I made too much information public?
* Have I made too little information public?
* Does this code make potential bugs screechingly obvious?
* Do I handle potential error conditions sensibly and completely?
* How much work do I face enhancing this code in the future?
PEP 8 concerns itself with far less interesting things, like why vertical alignment is annoying. In my experience, that's one of the least substantial elements contributing to maintainability.
As for readability, it doesn't really matter if someone who doesn't know the language can't read it.