| commit | 42c83afd14e1c7270124e581e42163ff5ef98ed8 | [log] [tgz] |
|---|---|---|
| author | Tim Peters <tim.peters@gmail.com> | Fri Sep 29 04:03:10 2000 +0000 |
| committer | Tim Peters <tim.peters@gmail.com> | Fri Sep 29 04:03:10 2000 +0000 |
| tree | ddd43b50a4149865a49aade1565d2535bcb9c805 | |
| parent | 3cc7e4d083916a5171caae453c38d423baae1d91 [diff] |
The 2.0b2 change to write .pyc files in exclusive mode (if possible) unintentionally caused them to get written in text mode under Windows. As a result, when .pyc files were later read-- in binary mode --the magic number was always wrong (note that .pyc magic numbers deliberately include \r and \n characters, so this was "good" breakage, 100% across all .pyc files, not random corruption in a subset). Fixed that.