[Python-Dev] Placement of os.fdopen functionality

Jp Calderone exarkun@intarweb.us
Fri, 11 Apr 2003 14:11:57 -0400

Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Apr 10, 2003 at 08:48:19PM -0400, Guido van Rossum wrote:
[Greg Ewing]
> > But since it is an os-dependent feature, the implementation
> > of it probably does belong in the os module.
> >=20
> > So how about providing a file.fromfd() which calls
> > os.fdopen()?
> I've never seen anyone code a file subclass yet, let alone one that
> needed this.  YAGNI?

  codecs.EncodedFile seems almost like it should (but it's just a factory
function).  Other than that I can't think of anything that does or that
would benefit from doing so.


Lowery's Law:
        If it jams -- force it.  If it breaks, it needed replacing anyway.
 up 22 days, 15:01, 3 users, load average: 1.05, 1.11, 1.16

Content-Type: application/pgp-signature
Content-Disposition: inline

Version: GnuPG v1.2.0 (GNU/Linux)