Greg Stein wrote:
>
> Even if we don't "complete the move", then we've still *improved* the
> situation.
I feel like the reorg is more likely to get done if we do it as we can
rather than waiting for someone to come along and do everything at once.
The standard library already feels so "messy" to me that I don't think
that use of packages in one place and not in another will confuse
anyone.
On the other hand, maybe we should only packagize things when we are
also going to make sure that they make sense as a collective. For
instance I would resist packaging binhex, uu, and binascii while they
have radically different interfaces. I will leave it up to those more in
the know to decide whether the "network" package would be coherent or
just a bag of related but not really integrated modules. A brief perusal
suggests that there is no such thing as a Gopher class (but then who
cares!). And should urlparse be part of urllib? etc.
--
Paul Prescod - ISOGEN Consulting Engineer speaking for himself
"The calculus and the rich body of mathematical analysis to which it
gave rise made modern science possible, but it was the algorithm that
made possible the modern world."
- from "Advent of the Algorithm" David Berlinski
http://www.opengroup.com/mabooks/015/0151003386.shtml
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