Guido van Rossum <gu...@python.org> added the comment: I am guessing the reason to keep os.popen() (albeit now reimplemented using subprocess) is that it is a convenient wrapper for a common use case and also familiar. I see no problem with this. (Indeed the big problem was with the proliferation of popenN with confusing signatures.) So I guess it ought to be documented and removed from the list of deprecations in 2.6.
---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6490> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
