|
| 1 | +Python Improved v2.0.0 |
| 2 | +====================== |
| 3 | + |
| 4 | +After much blood (well, a little), sweat (sorry, it's a gland problem), and tears |
| 5 | +(yup, some), version 2.0 is finally here! It was originally timed to coincide |
| 6 | +with the release of Python 3.5 a few weeks ago, but a particularly nasty bug |
| 7 | +reared its ugly head at the last minute (like usual) and threatened to end the |
| 8 | +whole party until @facelessuser rode to the rescue at the last minute and saved |
| 9 | +the day! This release is dedicated to him. Thanks, buddy! |
| 10 | + |
| 11 | +There have been *many* changes in PI. First and foremost, Unicode is now supported |
| 12 | +pretty much everywhere. That means you can name a function (or any identifier you |
| 13 | +want) Привет_мир, or 我喜欢奶酪, or Kolbász_finom, or whatever you like. Sublime |
| 14 | +Text 2 seems to have issues with some Unicode, especially combining marks, so if |
| 15 | +you find a bug first upgrade to Sublime Text 3 (http://sublimetext.com/3 or /3dev) |
| 16 | +to see if that helps. |
| 17 | + |
| 18 | +Other than that, a lot of work has been done internally to reorganize things, and |
| 19 | +clearly define if something is, for example, the name of a builtin function or a |
| 20 | +builtin function being called. For you Python 2 fans out there, `print` without |
| 21 | +parentheses is now scoped as a keyword, but with parens is a builtin function. All |
| 22 | +of the builtins, magic methods/attributes, errors, keywords and so on have been |
| 23 | +updated for Python 3.5, while still retaining all of the Python 2.7 ones. At last, |
| 24 | +... is highlighted as support.type.ellipsis. |
| 25 | + |
| 26 | +To take full advantage of the extra scopes included in Python Improved, check out |
| 27 | +the Neon Color Scheme at https://sublime.wbond.net/packages/Neon%20Color%20Scheme |
| 28 | +If you'd rather modify your own color scheme, a list of scopes is included in |
| 29 | +the README.md on GitHub at https://github.com/MattDMo/PythonImproved#readme |
| 30 | + |
| 31 | +If you have any questions, comments, concerns, bugs, or patches, please open an |
| 32 | +issue or pull request on GitHub and I'll do what I can to help out. You can also |
| 33 | +email me directly at < [email protected]> or find me on Twitter at @MattDMo. |
| 34 | +This is definitely a work in progress, so if you'd like to contribute I'd love |
| 35 | +to hear from you! |
0 commit comments