pool/python-Cython
SHA256
17
0
Fork 3
Code Issues Pull Requests Activity

Accepting request 204142 from devel:languages:python

Browse Source 
- update to 0.19.2:
    * Some standard declarations were fixed or updated, including the previously
    incorrect declaration of ``PyBuffer_FillInfo()`` and some missing bits in
    ``libc.math``.
    * Heap allocated subtypes of ``type`` used the wrong base type struct at the
    C level.
    * Calling the unbound method dict.keys/value/items() in dict subtypes could
    call the bound object method instead of the unbound supertype method.
    * "yield" wasn't supported in "return" value expressions.
    * Using the "bint" type in memory views lead to unexpected results.
    It is now an error.
    * Assignments to global/closure variables could catch them in an illegal state
    while deallocating the old value. (forwarded request 204137 from dirkmueller)

OBS-URL: https://build.opensuse.org/request/show/204142
OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/python-Cython?expand=0&rev=17
This commit is contained in:
Tomáš Chvátal
2013-10-21 18:01:30 +00:00
committed by Git OBS Bridge
parent 1223227d14
commit 1251b6d99a
4 changed files with 26 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
python-Cython.changes
View File

@@ -1,3 +1,25 @@
-------------------------------------------------------------------
Mon Oct 21 12:13:57 UTC 2013 - dmueller@suse.com
- update to 0.19.2:
* Some standard declarations were fixed or updated, including the previously
incorrect declaration of ``PyBuffer_FillInfo()`` and some missing bits in
``libc.math``.
* Heap allocated subtypes of ``type`` used the wrong base type struct at the
C level.
* Calling the unbound method dict.keys/value/items() in dict subtypes could
call the bound object method instead of the unbound supertype method.
* "yield" wasn't supported in "return" value expressions.
* Using the "bint" type in memory views lead to unexpected results.
It is now an error.
* Assignments to global/closure variables could catch them in an illegal state
while deallocating the old value.
-------------------------------------------------------------------
Fri Oct 11 17:06:20 UTC 2013 - p.drouand@gmail.com