| Georg Brandl | b80f511 | 2012-09-30 09:11:58 +0200 | [diff] [blame^] | 1 | **************************** |
| 2 | What's New In Python 3.4 |
| 3 | **************************** |
| 4 | |
| 5 | :Release: |release| |
| 6 | :Date: |today| |
| 7 | |
| 8 | .. Rules for maintenance: |
| 9 | |
| 10 | * Anyone can add text to this document. Do not spend very much time |
| 11 | on the wording of your changes, because your text will probably |
| 12 | get rewritten to some degree. |
| 13 | |
| 14 | * The maintainer will go through Misc/NEWS periodically and add |
| 15 | changes; it's therefore more important to add your changes to |
| 16 | Misc/NEWS than to this file. |
| 17 | |
| 18 | * This is not a complete list of every single change; completeness |
| 19 | is the purpose of Misc/NEWS. Some changes I consider too small |
| 20 | or esoteric to include. If such a change is added to the text, |
| 21 | I'll just remove it. (This is another reason you shouldn't spend |
| 22 | too much time on writing your addition.) |
| 23 | |
| 24 | * If you want to draw your new text to the attention of the |
| 25 | maintainer, add 'XXX' to the beginning of the paragraph or |
| 26 | section. |
| 27 | |
| 28 | * It's OK to just add a fragmentary note about a change. For |
| 29 | example: "XXX Describe the transmogrify() function added to the |
| 30 | socket module." The maintainer will research the change and |
| 31 | write the necessary text. |
| 32 | |
| 33 | * You can comment out your additions if you like, but it's not |
| 34 | necessary (especially when a final release is some months away). |
| 35 | |
| 36 | * Credit the author of a patch or bugfix. Just the name is |
| 37 | sufficient; the e-mail address isn't necessary. |
| 38 | |
| 39 | * It's helpful to add the bug/patch number as a comment: |
| 40 | |
| 41 | XXX Describe the transmogrify() function added to the socket |
| 42 | module. |
| 43 | (Contributed by P.Y. Developer in :issue:`12345`.) |
| 44 | |
| 45 | This saves the maintainer the effort of going through the Mercurial log |
| 46 | when researching a change. |
| 47 | |
| 48 | This article explains the new features in Python 3.4, compared to 3.3. |
| 49 | |
| 50 | .. Python 3.4 was released on September 29, 2012. |
| 51 | |
| 52 | For full details, see the :source:`Misc/NEWS` file. |
| 53 | |
| 54 | .. note:: Prerelease users should be aware that this document is currently in |
| 55 | draft form. It will be updated substantially as Python 3.4 moves towards |
| 56 | release, so it's worth checking back even after reading earlier versions. |
| 57 | |
| 58 | |
| 59 | .. seealso:: |
| 60 | |
| 61 | .. :pep:`4XX` - Python 3.4 Release Schedule |
| 62 | |
| 63 | |
| 64 | Summary -- Release highlights |
| 65 | ============================= |
| 66 | |
| 67 | .. This section singles out the most important changes in Python 3.3. |
| 68 | Brevity is key. |
| 69 | |
| 70 | New syntax features: |
| 71 | |
| 72 | * None yet. |
| 73 | |
| 74 | New library modules: |
| 75 | |
| 76 | * None yet. |
| 77 | |
| 78 | New built-in features: |
| 79 | |
| 80 | * None yet. |
| 81 | |
| 82 | Implementation improvements: |
| 83 | |
| 84 | * None yet. |
| 85 | |
| 86 | Significantly Improved Library Modules: |
| 87 | |
| 88 | * None yet. |
| 89 | |
| 90 | Security improvements: |
| 91 | |
| 92 | * None yet. |
| 93 | |
| 94 | Please read on for a comprehensive list of user-facing changes. |
| 95 | |
| 96 | |
| 97 | .. PEP-sized items next. |
| 98 | |
| 99 | .. _pep-4XX: |
| 100 | |
| 101 | .. PEP 4XX: Virtual Environments |
| 102 | .. ============================= |
| 103 | |
| 104 | |
| 105 | .. (Implemented by Foo Bar.) |
| 106 | |
| 107 | .. .. seealso:: |
| 108 | |
| 109 | :pep:`4XX` - Python Virtual Environments |
| 110 | PEP written by Carl Meyer |
| 111 | |
| 112 | |
| 113 | |
| 114 | |
| 115 | Other Language Changes |
| 116 | ====================== |
| 117 | |
| 118 | Some smaller changes made to the core Python language are: |
| 119 | |
| 120 | * None yet. |
| 121 | |
| 122 | |
| 123 | |
| 124 | New Modules |
| 125 | =========== |
| 126 | |
| 127 | .. module name |
| 128 | .. ----------- |
| 129 | |
| 130 | * None yet. |
| 131 | |
| 132 | |
| 133 | Improved Modules |
| 134 | ================ |
| 135 | |
| 136 | * None yet. |
| 137 | |
| 138 | |
| 139 | Optimizations |
| 140 | ============= |
| 141 | |
| 142 | Major performance enhancements have been added: |
| 143 | |
| 144 | * None yet. |
| 145 | |
| 146 | |
| 147 | Build and C API Changes |
| 148 | ======================= |
| 149 | |
| 150 | Changes to Python's build process and to the C API include: |
| 151 | |
| 152 | * None yet. |
| 153 | |
| 154 | |
| 155 | Deprecated |
| 156 | ========== |
| 157 | |
| 158 | Unsupported Operating Systems |
| 159 | ----------------------------- |
| 160 | |
| 161 | * None yet. |
| 162 | |
| 163 | |
| 164 | Deprecated Python modules, functions and methods |
| 165 | ------------------------------------------------ |
| 166 | |
| 167 | * None yet. |
| 168 | |
| 169 | |
| 170 | Deprecated functions and types of the C API |
| 171 | ------------------------------------------- |
| 172 | |
| 173 | * None yet. |
| 174 | |
| 175 | |
| 176 | Deprecated features |
| 177 | ------------------- |
| 178 | |
| 179 | * None yet. |
| 180 | |
| 181 | |
| 182 | Porting to Python 3.3 |
| 183 | ===================== |
| 184 | |
| 185 | This section lists previously described changes and other bugfixes |
| 186 | that may require changes to your code. |
| 187 | |
| 188 | * Nothing yet. |