Lerking/Phoenix
1
0
Fork 0
mirror of https://github.com/wxWidgets/Phoenix.git synced 2026-01-06 20:10:08 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

Minor text tweaks

Browse Source
This commit is contained in:
Robin Dunn
2017-04-12 10:45:15 -07:00
parent 01105def28
commit 085b9d1c99
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
CHANGES.rst
View File

@@ -16,7 +16,7 @@ ways:
* It's the first real release of Phoenix, which is built on a different
foundation than Classic wxPython was.
* It's the first wxPython release intended to be available from PyPI and
* It's the first wxPython release intended to be fully available from PyPI and
buildable/installable by pip.
* It's the first release for Python 3.
@@ -29,7 +29,7 @@ for them.
Due to some things being cleaned up, reorganized, simplified and dehackified
wxPython Phoenix is not completely backwards compatible with wxPython Classic.
This is as intended. In general, however, the API differences tend to be minor
This is intended. In general, however, the API differences tend to be minor
and some applications can use Phoenix with slight, or even no modifications.
In some other cases the correct way to do things was also available in Classic
and it's only the wrong way that has been removed from Phoenix. For more

2
docs/MigrationGuide.rst
View File

@@ -26,7 +26,7 @@ The version numbers for wxPython are no longer kept in sync with the wxWidgets
version number. In the past the common version number was used to indicate
exactly which version of wxWidgets should be used for the wxPython build. Now
wxWidgets is a git submodule, and the linked version is included in the
wxPython source tarball there is no longer any need to use the matching
wxPython source tarball, so there is no longer any need to use the matching
version numbers to implicitly specify the version of the wxWidgets source to
use.