diff options
| author | bors <bors@rust-lang.org> | 2017-10-17 00:34:32 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2017-10-17 00:34:32 +0000 |
| commit | 90691c8c1f8b4ece2a4f831a130ae087056b0083 (patch) | |
| tree | 900923f73be49d980752485af4cc8f456796931e /src/libstd/sys/unix/stack_overflow.rs | |
| parent | 5618aba38058dc700437b74cca52d139db1b337c (diff) | |
| parent | bd8497884c2863a10b6d67855bd90d40783ce2da (diff) | |
| download | rust-90691c8c1f8b4ece2a4f831a130ae087056b0083.tar.gz rust-90691c8c1f8b4ece2a4f831a130ae087056b0083.zip | |
Auto merge of #45138 - johnthagen:future_imports, r=nikomatsakis
Add more __future__ imports to increase compatibility with Python 3 in bootstrap The functionality of the `__future__` imports are described [here](https://docs.python.org/3/library/__future__.html). These will help ensure the bootstrap code stays compatible with Python 3. If changes are made in the future that use absolute imports, division, or the `print` function, this will be ensure that running it under Python 2 will pass or fail the same way as Python 3. `Option` is made a [new-style class](https://docs.python.org/2/reference/datamodel.html#new-style-and-classic-classes), so that it behaves the same way in Python 2 and 3. The `__future__ unicode_literals` import is not used, because that can change the semantics of the code in Python 2 in unwanted ways. For more information see [this article](http://python-future.org/unicode_literals.html).
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions
