From: Robin Dunn Date: Tue, 30 Mar 2004 21:46:20 +0000 (+0000) Subject: More notes about the type conversion fragment. X-Git-Url: https://git.saurik.com/wxWidgets.git/commitdiff_plain/33ab916f29844bbbb21f17a49ccd5a6ba1a8a27e More notes about the type conversion fragment. Cross linked CHANGES and MigrarionGuide. git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@26508 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775 --- diff --git a/wxPython/docs/CHANGES.html b/wxPython/docs/CHANGES.html index ca50576037..55ca17a8b7 100644 --- a/wxPython/docs/CHANGES.html +++ b/wxPython/docs/CHANGES.html @@ -12,7 +12,7 @@

Recent Changes for wxPython

2.5.1.4

-

(See also the MigrationGuide.txt file for details about some of the +

(See also the MigrationGuide file for details about some of the big changes that have happened in this release and how you should adapt your code.)

The wxWindows project and library is now known as wxWidgets. Please diff --git a/wxPython/docs/CHANGES.txt b/wxPython/docs/CHANGES.txt index d4e039362b..c94beec6e0 100644 --- a/wxPython/docs/CHANGES.txt +++ b/wxPython/docs/CHANGES.txt @@ -4,10 +4,13 @@ Recent Changes for wxPython 2.5.1.4 ------- -(See also the MigrationGuide.txt file for details about some of the +(See also the MigrationGuide_ file for details about some of the big changes that have happened in this release and how you should adapt your code.) +.. _MigrationGuide: MigrationGuide.html + + The wxWindows project and library is now known as wxWidgets. Please see http://www.wxwindows.org/name.htm for more details. This won't really affect wxPython all that much, other than the fact that the diff --git a/wxPython/docs/MigrationGuide.html b/wxPython/docs/MigrationGuide.html index afa8f5db6b..3aab1df56f 100644 --- a/wxPython/docs/MigrationGuide.html +++ b/wxPython/docs/MigrationGuide.html @@ -12,7 +12,7 @@

wxPython 2.5 Migration Guide

This document will help explain some of the major changes in wxPython 2.5 and let you know what you need to do to adapt your programs to -those changes. Be sure to also check in the CHANGES.txt file like +those changes. Be sure to also check in the CHANGES file like usual to see info about the not so major changes and other things that have been added to wxPython.

@@ -555,6 +555,26 @@ when your last Frame is closed. For wxPython apps it is usually enough if your main frame object holds the only reference to the wx.TaskBarIcon, then when the frame is closed Python reference counting takes care of the rest.

+

Before Python 2.3 it was possible to pass a floating point object as a +parameter to a function that expected an integer, and the +PyArg_ParseTuple family of functions would automatically convert to +integer by truncating the fractional portion of the number. With +Python 2.3 that behavior was deprecated and a deprecation warning is +raised when you pass a floating point value, (for example, calling +wx.DC.DrawLineXY with floats for the position and size,) and lots of +developers using wxPython had to scramble to change their code to call +int() before calling wxPython methods. Recent changes in SWIG have +moved the conversion out of PyArg_ParseTuple to custom code that SWIG +generates. Since the default conversion fragment was a little too +strict and didn't generate a very meaningful exception when it failed, +I decided to use a custom fragment instead, and it turned out that +it's very easy to allow floats to be converted again just like they +used to be. So, in a nutshell, any numeric type that can be +converted to an integer is now legal to be passed to SWIG wrapped +functions in wxPython for parameters that are expecting an integer. +If the object is not already an integer then it will be asked to +convert itself to one. A similar conversion fragment is in place for +parameters that expect floating point values.

diff --git a/wxPython/docs/MigrationGuide.txt b/wxPython/docs/MigrationGuide.txt index e5e2c59617..476c60252d 100644 --- a/wxPython/docs/MigrationGuide.txt +++ b/wxPython/docs/MigrationGuide.txt @@ -4,10 +4,12 @@ wxPython 2.5 Migration Guide This document will help explain some of the major changes in wxPython 2.5 and let you know what you need to do to adapt your programs to -those changes. Be sure to also check in the CHANGES.txt file like +those changes. Be sure to also check in the CHANGES_ file like usual to see info about the not so major changes and other things that have been added to wxPython. +.. _CHANGES: CHANGES.html + wxName Change ------------- @@ -626,3 +628,23 @@ enough if your main frame object holds the only reference to the wx.TaskBarIcon, then when the frame is closed Python reference counting takes care of the rest. +Before Python 2.3 it was possible to pass a floating point object as a +parameter to a function that expected an integer, and the +PyArg_ParseTuple family of functions would automatically convert to +integer by truncating the fractional portion of the number. With +Python 2.3 that behavior was deprecated and a deprecation warning is +raised when you pass a floating point value, (for example, calling +wx.DC.DrawLineXY with floats for the position and size,) and lots of +developers using wxPython had to scramble to change their code to call +int() before calling wxPython methods. Recent changes in SWIG have +moved the conversion out of PyArg_ParseTuple to custom code that SWIG +generates. Since the default conversion fragment was a little too +strict and didn't generate a very meaningful exception when it failed, +I decided to use a custom fragment instead, and it turned out that +it's very easy to allow floats to be converted again just like they +used to be. So, in a nutshell, any numeric type that can be +converted to an integer is now legal to be passed to SWIG wrapped +functions in wxPython for parameters that are expecting an integer. +If the object is not already an integer then it will be asked to +convert itself to one. A similar conversion fragment is in place for +parameters that expect floating point values.