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/2003-February/033409.html below:

[Python-Dev] import curdir,pardir,sep,pathsep,defpath from relevant *path module

[Python-Dev] import curdir,pardir,sep,pathsep,defpath from relevant *path moduleMichael Hudson mwh@python.net
Fri, 14 Feb 2003 11:13:25 +0000
Skip Montanaro <skip@pobox.com> writes:

> Proposal: Move the definitions of curdir, pardir, sep, pathsep and defpath
> into the relevant path module (ntpath, posixpath, etc), then for
> compatibility reimport them ("from path import curdir, pardir, sep, pathsep,
> defpath") later in os.py.  Update the libref documentation to reflect these
> items' new home.  Do whatever is necessary deprecation-wise (silent in 2.3?
> Update usage in Python source after 2.3 release and add visible deprecation
> in 2.4?).

I know Guido's squashed the idea, but how would you issue a warning on
use of a module level global?

Cheers,
M.

-- 
  This makes it possible to pass complex object hierarchies to
  a C coder who thinks computer science has made no worthwhile
  advancements since the invention of the pointer.
                                       -- Gordon McMillan, 30 Jul 1998



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