diff options
author | 2016-02-12 17:05:34 -0800 | |
---|---|---|
committer | 2016-02-12 17:35:08 -0800 | |
commit | 5fd21f652ff36f7a6abea7f8745840113b454b46 (patch) | |
tree | 3c3d8e7e2d40f7eb34cda9d46b3573bdf5e23774 /tensorflow/g3doc/resources/faq.md | |
parent | 6d46c0b370836698a3195a6d73398f15fa44bcb2 (diff) |
TensorFlow: update faq to remove platform import issue, since
it's no longer necessary.
Change: 114584189
Diffstat (limited to 'tensorflow/g3doc/resources/faq.md')
-rw-r--r-- | tensorflow/g3doc/resources/faq.md | 9 |
1 files changed, 0 insertions, 9 deletions
diff --git a/tensorflow/g3doc/resources/faq.md b/tensorflow/g3doc/resources/faq.md index 1a8a1b1824..bf96ecd442 100644 --- a/tensorflow/g3doc/resources/faq.md +++ b/tensorflow/g3doc/resources/faq.md @@ -317,12 +317,3 @@ The TensorFlow C++ code base adheres to the (<sup>*</sup> With one exception: we use 2-space indentation instead of 4-space indentation.) -#### Why do we disable bad import lint warnings in many of our Python scripts? - -Because we run TensorFlow in Google's internal code environment too, there are -import dependencies that require us to pull in -`third_party.tensorflow.python.platform` first before other modules. This -doesn't apply externally, but to allow reuse of the scripts in both environments -we keep the import order, and disable warnings around this special case. - -We're hoping to create a better solution to this in the future. |