PEP on path module for standard library
gsakkis at rutgers.edu
Fri Jul 22 02:29:23 CEST 2005
"John Roth" <newsgroups at jhrothjr.com> wrote:
> "Reinhold Birkenfeld" <reinhold-birkenfeld-nospam at wolke7.net> wrote
> > He said,
> > """
> > Whoa! Do we really need a completely different mechanism for doing the
> > same stuff we can already do? The path module seems mostly useful for
> > folks coming from Java who are used to the Java Path class. With the
> > massive duplication of functionality we should also consider what to
> > recommend for the future: will the old os.path module be deprecated,
> > or are we going to maintain both alternatives forever? (And what about
> > all the duplication with the os module itself, like the cwd()
> > constructor?) Remember TOOWTDI.
> > """
> Read literally, this says (at least to me) "I don't want to fix it because
> I don't think it's broke."
Or rather "I prefer a single existing mediocre solution than two solutions (even if the second was
More information about the Python-list