Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Gwenaël Samain
cython
Commits
0105dd2c
Commit
0105dd2c
authored
Apr 19, 2013
by
Stefan Behnel
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
changelog
parent
b330bba3
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
5 deletions
+5
-5
CHANGES.rst
CHANGES.rst
+5
-5
No files found.
CHANGES.rst
View file @
0105dd2c
...
@@ -52,11 +52,6 @@ Features added
...
@@ -52,11 +52,6 @@ Features added
are automatically mapped to the equivalent keys/values/items methods in Python 3
are automatically mapped to the equivalent keys/values/items methods in Python 3
for typed dictionaries.
for typed dictionaries.
* 2-value slicing of unknown objects passes the correct slice when the ``getitem``
protocol is used instead of the ``getslice`` protocol (especially in Python 3),
i.e. ``None`` values for missing bounds instead of ``[0,maxsize]``. It is also
a bit faster in some cases, e.g. for constant bounds. This fixes trac ticket 636.
* Slicing unicode strings, lists and tuples is faster.
* Slicing unicode strings, lists and tuples is faster.
* list.append() is faster on average.
* list.append() is faster on average.
...
@@ -73,6 +68,11 @@ Features added
...
@@ -73,6 +68,11 @@ Features added
Bugs fixed
Bugs fixed
----------
----------
* 2-value slicing of unknown objects passes the correct slice when the ``getitem``
protocol is used instead of the ``getslice`` protocol (especially in Python 3),
i.e. ``None`` values for missing bounds instead of ``[0,maxsize]``. It is also
a bit faster in some cases, e.g. for constant bounds. This fixes trac ticket 636.
* Cascaded assignments of None values to extension type variables failed with
* Cascaded assignments of None values to extension type variables failed with
a ``TypeError`` at runtime.
a ``TypeError`` at runtime.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment