A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2008-September/082118.html below:

[Python-Dev] Further PEP 8 compliance issues in threading and multiprocessing

[Python-Dev] Further PEP 8 compliance issues in threading and multiprocessing [Python-Dev] Further PEP 8 compliance issues in threading and multiprocessingAntoine Pitrou solipsis at pitrou.net
Mon Sep 1 16:36:00 CEST 2008
Nick Coghlan <ncoghlan <at> gmail.com> writes:
> 
> Is this just intended to discourage subclassing? If so, why give the
> misleading impression that these things can be subclassed by naming them
> as if they were classes?
> 
> How should this be handled when it comes to the addition of PEP 8
> compliant aliases?

I don't see a problem for trivial functional wrappers to classes to be
capitalized like classes. So I'd suggest option 3: leave it as-is. Otherwise
option 2 (replace the wrappers with the actual classes) has my preference.



More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4