> There is value in having non-trivial coverage of the language. When people
> ask how
> __cause__ works, we can link to the tutorial.
I don't necessarily agree with the rest, but I think this is very important -
at least, in the
current situation. Maybe in the future we will be able to rear
> I suspect that future documentation will have "How Tos" being more often
> written to cover more technical topics in detail. These more standalone
> "How Tos" can then be linked to from contents and search pages.
Indeed. Take for instance the most recent addition, regarding special
parameters
Hi Kyle,
> ... I think that we should use the
> guideline of: "Is this useful information in 95% of real-world use cases or
> does it have a strong niche purpose that will be useful at some point for
> significant number of Python users?" If not, my opinion is that it should
> be removed ...
I'm
Inada,
as I said before, mine was more a general consideration than a criticism of a
particular change (let alone a particular committer!).
> But the tutorial isn't a "special attribute showcase".
> It doesn't cover all special attributes and describe how Python
> interpreter use the special att
Hi Inada,
> Note that the discussion not only in the b.p.o thread, but in this
> mailing list too.
> Please read this long thread.
I have, but I don't know if I want to step in...
I do have, indeed, opinions (and some expertise) on the matter, but
I've never really thought about it in depth...
Dear all,
I am the maintainer of an Italian translation of the Python Tutorial:
https://pytutorial-it.readthedocs.io.
Since the Italian translation is kept in sync with the original repo (across
all the branches!), from time to time I get an alert when a change is
committed.
This morning I
