tf.gfile is now tf.io.gfile.
PiperOrigin-RevId: 293818901 Change-Id: I51746a055ca608a2a8b0cfb8696f7f33ca84fd53
This commit is contained in:
parent
bc1459f360
commit
925be1049d
@ -41,21 +41,21 @@ from tensorflow.python.util.tf_export import tf_export
|
|||||||
class GFile(_FileIO):
|
class GFile(_FileIO):
|
||||||
"""File I/O wrappers without thread locking.
|
"""File I/O wrappers without thread locking.
|
||||||
|
|
||||||
The main roles of the `tf.gfile` module are:
|
The main roles of the `tf.io.gfile` module are:
|
||||||
|
|
||||||
1. To provide an API that is close to Python's file I/O objects, and
|
1. To provide an API that is close to Python's file I/O objects, and
|
||||||
2. To provide an implementation based on TensorFlow's C++ FileSystem API.
|
2. To provide an implementation based on TensorFlow's C++ FileSystem API.
|
||||||
|
|
||||||
The C++ FileSystem API supports multiple file system implementations,
|
The C++ FileSystem API supports multiple file system implementations,
|
||||||
including local files, Google Cloud Storage (using a `gs://` prefix, and
|
including local files, Google Cloud Storage (using a `gs://` prefix, and
|
||||||
HDFS (using an `hdfs://` prefix). TensorFlow exports these as `tf.gfile`,
|
HDFS (using an `hdfs://` prefix). TensorFlow exports these as `tf.io.gfile`,
|
||||||
so that you can use these implementations for saving and loading checkpoints,
|
so that you can use these implementations for saving and loading checkpoints,
|
||||||
writing to TensorBoard logs, and accessing training data (among other uses).
|
writing to TensorBoard logs, and accessing training data (among other uses).
|
||||||
However, if all your files are local, you can use the regular Python file
|
However, if all your files are local, you can use the regular Python file
|
||||||
API without any problem.
|
API without any problem.
|
||||||
|
|
||||||
*Note*: though similar to Python's I/O implementation, there are semantic
|
*Note*: though similar to Python's I/O implementation, there are semantic
|
||||||
differences to make `tf.gfile` more efficient for backing filesystems. For
|
differences to make `tf.io.gfile` more efficient for backing filesystems. For
|
||||||
example, a write mode file will not be opened until the first write call, to
|
example, a write mode file will not be opened until the first write call, to
|
||||||
minimize RPC invocations in network filesystems.
|
minimize RPC invocations in network filesystems.
|
||||||
"""
|
"""
|
||||||
|
Loading…
Reference in New Issue
Block a user