Re: Current plan for Phoenix

Hi,

This is really exciting!

Can I suggest inserting into the plan some pre-release announcements to 
multiple mailing lists / forums, something like this:

Although Phoenix is not yet stable, now is a good time to try it with your 
wxPython application (and post feedback to the appropriate mailing list or 
GitHub Issues page) because:

1. wxPython classic is not being actively developed, whereas Phoenix 
snapshots are being updated regularly with a focus on fixing bugs and 
enhancing documentation (not adding major new features which are likely to 
cause instability).

2. The wheel installation method has several advantages:
(i) Easy to install automatically for Continuous Integration builds.
      Maybe list some open source projects already using Phoenix wheels for 
CI?
(ii) Installation doesn't require admin privileges (or tweaking security 
settings on macOS).
 ...

3. Quick responses are expected for bug reports, as seen on the Phoenix 
GitHub Issues page.

4. End of life for Python 2 is coming: 
https://www.python.org/dev/peps/pep-0373/#id2

5. It should be possible to make your application compatible with both 
classic and Phoenix and avoid deprecation warnings, e.g.

    if wx.version().startswith("3.0.3.dev"):

        busyCursor = wx.Cursor(wx.CURSOR_WAIT)

    else:

        busyCursor = wx.StockCursor(wx.CURSOR_WAIT)

Cheers,
James

-- 
You received this message because you are subscribed to the Google Groups "wxPython-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.