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/2013-September/128365.html below:

[Python-Dev] SEEK_* constants in io and os

[Python-Dev] SEEK_* constants in io and os [Python-Dev] SEEK_* constants in io and osEthan Furman ethan at stoneleaf.us
Fri Sep 6 16:23:46 CEST 2013
On 09/01/2013 06:02 PM, Eli Bendersky wrote:
>
> os seems to import io in some functions; can this be done always? If yes, we can just define the constants once and
> os.SEEK_* will alias io.SEEK_*? The other way (io taking from os) is also a possibility (maybe the preferred one because
> io already refers to os.SEEK_HOLE/DATA, at least in the documentation).
>
> Any ideas and suggestions are welcome,

Ideally we should only define them once.

If these are values that could change per O/S then they should be in the os module.  Since they /can/ change per O/S 
(even if they don't currently), we should put them in os.

I'd say it's worth the extra 0.5ms startup time.

--
~Ethan~
More information about the Python-Dev mailing list

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