Message 123169 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	belopolsky
Recipients	Rodolpho.Eckhardt, belopolsky, brian.curtin, eric.araujo, georg.brandl, henriquebastos, robcliffe, ron_adam, terry.reedy
Date	2010-12-03.03:02:16
SpamBayes Score	1.6960772e-06
Marked as misclassified	No
Message-id	<AANLkTimFSXdjOZWLKThpV-04f3eB9NViK01guRTvZDR=@mail.gmail.com>
In-reply-to	<1291345000.26.0.283238546656.issue8525@psf.upfronthosting.co.za>

Content
On Thu, Dec 2, 2010 at 9:56 PM, Éric Araujo <report@bugs.python.org> wrote: .. > Didn’t the first message ask for the feature to be extended to non-exceptions classes? “Built-in” > subclasses is a red herring, to me the feature is: display subclasses. In the text output you can use > the search feature of your pager to jump to a subclass, in the HTML output it would be a helpful link. If we don't restrict to builtins, then the display will depend on what modules are currently loaded and will be useless for command line use unless all subclasses are defined in the same module.

On Thu, Dec 2, 2010 at 9:56 PM, Éric Araujo <report@bugs.python.org> wrote:
..
> Didn’t the first message ask for the feature to be extended to non-exceptions classes?  “Built-in”
> subclasses is a red herring, to me the feature is: display subclasses.  In the text output you can use
> the search feature of your pager to jump to a subclass, in the HTML output it would be a helpful link.

If we don't restrict to builtins, then the display will depend on what
modules are currently loaded and will be useless for command line use
unless all subclasses are defined in the same module.

History
Date	User	Action	Args
2010-12-03 03:02:20	belopolsky	set	recipients: + belopolsky, georg.brandl, terry.reedy, ron_adam, eric.araujo, brian.curtin, robcliffe, henriquebastos, Rodolpho.Eckhardt
2010-12-03 03:02:16	belopolsky	link	issue8525 messages
2010-12-03 03:02:16	belopolsky	create