DLL name change in 2.4.0.7?

wxPython Users
1

Hi!

I just noted that the wxPython dll stored in
C:\Python22\Lib\site-packages\wxPython changed its name from version
2.4.0.2 to 2.4.0.7. It used to be called "wxmsw240h.dll", but now it is
called "wxmsw24h.dll" (a zero disappeared from the name).

This was kind of important since we used the presence of that file to
see if WxPython 2.4.0 was installed on a user machine.

Is there a better way to do this?

Is the name change permanent for future versions?

/jakob

···

------------------------------------------------------------
      Jakob Engblom, PhD. Senior developer @ Virtutech
                           & Adjunct Professor @ Uppsala U
------------------------------------------------------------

       WWW: www.virtutech.com
     Email: jakob@virtutech.com
     Phone: +46-(0)8-6900746
       Fax: +46-(0)8-6900729

    University home: http://user.it.uu.se/~jakob

2

Jakob Engblom wrote:

Hi!

I just noted that the wxPython dll stored in
C:\Python22\Lib\site-packages\wxPython changed its name from version
2.4.0.2 to 2.4.0.7. It used to be called "wxmsw240h.dll", but now it is
called "wxmsw24h.dll" (a zero disappeared from the name).

Yes, it should have been gone in the 2.4.0 release too but it was overlooked. Since all 2.4 releases are supposed to be binary backwards compatible it was decided that only the first two components of the version were needed.

This was kind of important since we used the presence of that file to
see if WxPython 2.4.0 was installed on a user machine.

Is there a better way to do this?

How about something like
  
  python -c "from wxPython import wx; print wx.__version__"

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

3

Jakob Engblom wrote:
> Hi!
>
> I just noted that the wxPython dll stored in
> C:\Python22\Lib\site-packages\wxPython changed its name
from version
> 2.4.0.2 to 2.4.0.7. It used to be called "wxmsw240h.dll",
but now it
> is called "wxmsw24h.dll" (a zero disappeared from the name).

Yes, it should have been gone in the 2.4.0 release too but it was
overlooked. Since all 2.4 releases are supposed to be binary
backwards
compatible it was decided that only the first two components of the
version were needed.

>
> This was kind of important since we used the presence of
that file to
> see if WxPython 2.4.0 was installed on a user machine.
>
> Is there a better way to do this?
>

How about something like
  
  python -c "from wxPython import wx; print wx.__version__"

Well, that assumes that Python is already present... but I guess we can
assume that if Python is not present, neither is wxWindows. And then
there is the issue on how to do that from inside an installshield
installer on Windows :slight_smile:

/jakob