blocks|key|2207364|text|os.open()方法打开文件文件，并根据标志设置各种标志，可能还会根据模式设置其模式。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2207365|默认模式为0777+(八进制)，当前未屏蔽值首先被屏蔽。|2207366|此方法返回新打开的文件的文件描述符。|2207367|同时，|2207368|io.open()方法以字符串模式中指定的模式打开文件。它返回一个新的文件句柄，如果出现错误，则返回nil加上一条错误消息。|2207369|希望这能有所帮助|2207370|entityMap^0|0|9|0|0|0|0|0|9|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|V|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|W|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|N|3|O|5|6|7|10|8|@]|D|@]|E|$]]|$1|P|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|Q|$]]

<code>os.open()</code> method opens the file file and set various flags according to flags and possibly its mode according to mode.

The default mode is 0777 (octal), and the current unmask value is first masked out.

This method returns the file descriptor for the newly opened file.

While,

<code>io.open()</code> method opens a file, in the mode specified in the string mode. It returns a new file handle, or, in case of errors, nil plus an error message. 

Hope this helps

blocks|key|2207396|text|io.open()是文件I/O的首选高级接口。它将操作系统级别的文件描述符包装在一个对象中，您可以使用该对象以Pythonic方式访问文件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2207397|os.open()只是一个低级POSIX+syscall的包装器。它采用较少的符号(和更多的POSIX-y)参数，并返回表示打开的文件的文件描述符(一个数字)。它不返回文件对象；返回值将没有read()或write()方法。|2207398|从os.open()+documentation|2207399|file此函数用于低级I/O。正常使用时，请使用内置函数open()，该函数返回带有read()和write()方法(以及更多方法)的“|2207400|对象”。|blockquote|2207401|2207402|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.python.org/library/os.html#os.open^0|0|9|0|0|9|2N|6|2U|7|0|1|9|1|N|0|0|S|6|16|6|1D|7|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|10|8|@$9|11|A|12|B|C]|$9|13|A|14|B|C]|$9|15|A|16|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|17|8|@$9|18|A|19|B|C]]|D|@$9|1A|A|1B|1|1C]]|E|$]]|$1|J|3|K|5|6|7|1D|8|@$9|1E|A|1F|B|C]|$9|1G|A|1H|B|C]|$9|1I|A|1J|B|C]]|D|@]|E|$]]|$1|L|3|M|5|N|7|1K|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|1L|8|@]|D|@]|E|$]]|$1|P|3|-4|5|6|7|1M|8|@]|D|@]|E|$]]]|Q|$R|$5|S|T|U|E|$V|W]]]]

<code>io.open()</code> is the preferred, higher-level interface to file I/O. It wraps the OS-level file descriptor in an object that you can use to access the file in a Pythonic manner.

<code>os.open()</code> is just a wrapper for the lower-level POSIX syscall. It takes less symbolic (and more POSIX-y) arguments, and returns the file descriptor (a number) that represents the opened file. It does not return a file object; the returned value will not have <code>read()</code> or <code>write()</code> methods.

From the <a href="http://docs.python.org/library/os.html#os.open" rel="noreferrer"><code>os.open()</code> documentation</a>:

<blockquote>
 This function is intended for low-level I/O. For normal usage, use the built-in function <code>open()</code>, which returns a “file object” with <code>read()</code> and <code>write()</code> methods (and many more). 
</blockquote>

blocks|key|2207416|text|os.open与open()+from+C+in+Unix非常相似。您不太可能想要使用它，除非您正在做一些更低级的事情。它为您提供了一个实际的文件描述符(例如，一个数字，而不是一个对象)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2207417|io.open是您的基本Python+open()，也是您想要一直使用的all。|2207418|entityMap|0|LINK|mutability|MUTABLE|url|http://linux.die.net/man/2/open^0|0|7|8|6|8|L|0|0|0|7|J|6|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@$9|U|A|V|1|W]]|E|$]]|$1|F|3|G|5|6|7|X|8|@$9|Y|A|Z|B|C]|$9|10|A|11|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

<code>os.open</code> is very similar to <a href="http://linux.die.net/man/2/open" rel="nofollow"><code>open()</code> from C in Unix</a>. You're unlikely to want to use it unless you're doing something much more low-level. It gives you an actual file descriptor (as in, a number, not an object).

<code>io.open</code> is your basic Python <code>open()</code> and what you want to use just about all the time.

blocks|key|336306|text|绝对的一切：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|336307|336308|os.open()将文件名作为字符串，将文件模式作为属性的逐位掩码，并以描述文件权限位的可选参数作为参数，以integer.|unordered-list-item|offset|length|style|CODE|336309|io.open()的形式返回文件描述符，将文件名作为字符串或文件描述符作为整数，将文件模式作为字符串，将描述文件编码、使用的缓冲、如何处理编码错误和换行符的可选参数，以及在关闭文件时是否关闭了底层FD，并返回io.IOBase.|336310|的某个后代|336311|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.python.org/2/library/os.html#os.open|1|https://docs.python.org/2/library/io.html#io.open^0|0|0|0|9|0|9|0|0|0|9|2W|9|0|9|1|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|Z|8|@$F|10|G|11|H|I]]|9|@$F|12|G|13|1|14]]|A|$]]|$1|J|3|K|5|E|7|15|8|@$F|16|G|17|H|I]|$F|18|G|19|H|I]]|9|@$F|1A|G|1B|1|1C]]|A|$]]|$1|L|3|M|5|6|7|1D|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]|V|$5|Q|R|S|A|$T|W]]]]

Absolutely everything:

<ul>
<li><a href="https://docs.python.org/2/library/os.html#os.open" rel="noreferrer"><code>os.open()</code></a> takes a filename as a string, the file mode as a bitwise mask of attributes, and an optional argument that describes the file permission bits, and returns a file descriptor as an integer.</li>
<li><a href="https://docs.python.org/2/library/io.html#io.open" rel="noreferrer"><code>io.open()</code></a> takes a filename as a string or a file descriptor as an integer, the file mode as a string, and optional arguments that describe the file encoding, buffering used, how encoding errors and newlines are handled, and if the underlying FD is closed when the file is closed, and returns some descendant of <code>io.IOBase</code>.</li>
</ul>

blocks|key|4106629|text|要添加到现有答案中，请执行以下操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4106630|我意识到我一直在使用的|4106631|+()函数是io.open()的别名|blockquote|4106632|4106633|4106634|仅Python3中的open()+==+io.open()。在Python+2中，它们是不同的。|offset|length|style|CODE|4106635|而在Python中使用open()，我们可以通过方便的read()和write()方法获得一个易于使用的文件对象，在操作系统级别上，文件是通过文件描述符(或文件句柄)来访问的。因此，os.open()应该在幕后隐式使用。我没有研究过这方面的Python源代码，但是在Python3.3中为open()添加的opener参数的文档中写道：|4106636|4106637|自定义打开程序可以通过传递一个callable作为打开程序来使用。文件对象的底层文件描述符然后通过使用(+file，flag)调用opener来获得。opener必须返回一个打开的文件描述符(作为opener传递os.open的功能类似于传递None)。|4106638|4106639|4106640|因此，os.open()是open()的默认打开程序，如果需要更改文件标志或模式，我们还可以在其周围指定自定义包装器。有关自定义打开程序的示例，请参阅open()的documentation，该打开程序相对于给定目录打开文件。|4106641|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.python.org/3/library/functions.html#open^0|0|0|0|0|0|A|6|K|9|0|B|6|R|6|Y|7|2J|9|40|6|49|6|0|0|2Y|7|3D|4|0|0|0|3|9|D|6|23|6|2A|D|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|16|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|17|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|19|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|1A|8|@$K|1B|L|1C|M|N]|$K|1D|L|1E|M|N]]|9|@]|A|$]]|$1|O|3|P|5|6|7|1F|8|@$K|1G|L|1H|M|N]|$K|1I|L|1J|M|N]|$K|1K|L|1L|M|N]|$K|1M|L|1N|M|N]|$K|1O|L|1P|M|N]|$K|1Q|L|1R|M|N]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1S|8|@]|9|@]|A|$]]|$1|R|3|S|5|F|7|1T|8|@$K|1U|L|1V|M|N]|$K|1W|L|1X|M|N]]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|20|8|@$K|21|L|22|M|N]|$K|23|L|24|M|N]|$K|25|L|26|M|N]]|9|@$K|27|L|28|1|29]]|A|$]]|$1|X|3|-4|5|6|7|2A|8|@]|9|@]|A|$]]]|Y|$Z|$5|10|11|12|A|$13|14]]]]

To add to the existing answers:

<blockquote>
 I realised that the open() function I've been using was an alias to io.open()
</blockquote>

<code>open()</code> == <code>io.open()</code> in Python 3 only. In Python 2 they are different.

While with <code>open()</code> in Python we can obtain an easy-to-use file object with handy <code>read()</code> and <code>write()</code> methods, on the OS level files are accessed using file descriptors (or file handles in Windows). Thus, <code>os.open()</code> should be used implicitly under the hood. I haven't examined Python source code in this regard, but the documentation for the <code>opener</code> parameter, which was added for <code>open()</code> in Python 3.3, says:

<blockquote>
 A custom opener can be used by passing a callable as opener. The
 underlying file descriptor for the file object is then obtained by
 calling opener with (file, flags). opener must return an open file
 descriptor (passing <code>os.open</code> as opener results in functionality similar
 to passing <code>None</code>).
</blockquote>

So <code>os.open()</code> is the default opener for <code>open()</code>, and we also have the ability to specify a custom wrapper around it if file flags or mode need to be changed. See the <a href="https://docs.python.org/3/library/functions.html#open" rel="nofollow noreferrer">documentation</a> for <code>open()</code> for an example of a custom opener, which opens a file relative to a given directory.

blocks|key|334935|text|数据库和系统应用程序开发人员通常使用open而不是fopen，因为前者对何时、什么以及如何将内存内容写入其后备存储器(即，磁盘上的文件)提供了更精细的控制。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|334936|在类Unix操作系统中，open用于打开常规文件、套接字端点、设备、管道等。每次成功的open函数调用都会返回一个正的文件描述符号。它提供了一个一致的API和框架来检查各种对象上的事件通知等。|334937|但是，fopen是一个标准C函数，通常用于打开常规文件并返回FILE数据结构。实际上，fopen最终会调用open。fopen对于正常使用来说已经足够好了，因为开发人员不需要担心何时将内存内容刷新或同步到磁盘，也不需要事件通知。|334938|entityMap^0|I|4|P|5|0|C|4|17|4|0|3|5|U|4|17|5|1H|4|1M|5|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|V|8|@$9|W|A|X|B|C]|$9|Y|A|Z|B|C]|$9|10|A|11|B|C]|$9|12|A|13|B|C]|$9|14|A|15|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|K|$]]

Database and system application developers usually use <code>open</code> instead of <code>fopen</code> as the former provides finer control on when, what and how the memory content should be written to its backing store (i.e., file on disk).

In Unix-like operating system, <code>open</code> is used to open regular file, socket end-point, device, pipe, etc. A positive file descriptor number is returned for every successful <code>open</code> function call. It provides a consistent API and framework to check for event notification, etc on a variety of these objects. 

However, <code>fopen</code> is a standard C function and is normally used to open regular file and return a <code>FILE</code> data structure. <code>fopen</code>, actually, will call <code>open</code> eventually. <code>fopen</code> is good enough for normal usage as developers do not need to worry when to flush or sync memory content to the disk and do not need event notification.

blocks|key|334958|text|在Python2中，内置的open和io.open是不同的(io.open比较新，支持的东西也更多)。在Python3中，open和io.open现在是一回事(它们去掉了旧的内置open)，所以您应该始终使用open。需要与Python2和3兼容的代码可能有使用io.open的理由。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|334959|下面的代码来验证这一点。|334960|import+io
with+io.open("../input/files.txt")+as+f:
++++text+=+f.read().lower()

with+open('../input/files.txt',+encoding='utf-8')+as+f2:
++++text2+=+f2.read().lower()

print(type(f))
print(type(f2))
#+<class+'_io.TextIOWrapper'>
#+<class+'_io.TextIOWrapper'>|code-block|syntax|javascript|334961|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

In Python 2, the built-in open and io.open were different (io.open was newer and supported more things). In Python 3, open and io.open are now the same thing (they got rid of the old built-in open), so you should always use open. Code that needs to be compatible with Python 2 and 3 might have a reason to use io.open.
Below code to validate this.
<pre><code>import io
with io.open(&quot;../input/files.txt&quot;) as f:
 text = f.read().lower()

with open('../input/files.txt', encoding='utf-8') as f2:
 text2 = f2.read().lower()

print(type(f))
print(type(f2))
# &lt;class '_io.TextIOWrapper'&gt;
# &lt;class '_io.TextIOWrapper'&gt;
</code></pre>

I realised that the <code>open()</code> function I've been using was an alias to <code>io.open()</code> and that importing <code>*</code> from <code>os</code> would overshadow that. 

What's the difference between opening files through the <code>io</code> module and <code>os</code> module?

What's the difference between io.open() and os.open() on Python?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我意识到我一直在使用的open()函数是io.open()的别名，从os导入*会使它黯然失色。通过io模块和os模块打开文件有什么不同？

问Python上的io.open()和os.open()有什么不同？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Python上的io.open()和os.open()有什么不同？EN