On Tue, 19 Jul 2011 23:58:55 -0400, "P.J. Eby" <pje at telecommunity.com> wrote: > Worse, this is not just a problem for new users: it prevents *anyone* > from easily splitting a package into separately-installable > components. In Perl terms, it would be as if every possible ``Net::`` > module on CPAN had to be bundled up and shipped in a single tarball! In general the simplicity of the proposed mechanism and implementation is attractive. However, this bit of discussion struck me as sending the wrong message. We don't *want* something like the CPAN module hierarchy. I prefer to keep things as flat as practical. Namespace packages clearly have utility, but please let's not descend into java-esq package hierarchies. -- R. David Murray http://www.bitdance.com
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