Hi Robin,
I have noticed for a while that even if nothing in the wxWindows / wxPython cvs changes, if you run setup.py build it always does:
copying wx/__version__.py -> build/lib.linux-i686-2.3/wx
and I was wondering why?
TIA
MarkL
Hi Robin,
I have noticed for a while that even if nothing in the wxWindows / wxPython cvs changes, if you run setup.py build it always does:
copying wx/__version__.py -> build/lib.linux-i686-2.3/wx
and I was wondering why?
TIA
MarkL
mlivingstone@iprimus.com.au wrote:
Hi Robin,
I have noticed for a while that even if nothing in the wxWindows / wxPython cvs changes, if you run setup.py build it always does:
copying wx/__version__.py -> build/lib.linux-i686-2.3/wx
and I was wondering why?
Because setup.py always writes a new version of that file to the src dir. Originally it was checking timestamps and only writing a new version if setup.py itself had changed, but then things changed so that the version number could differ based on the UNICODE flag which could be specified on the command line, so I couldn't depend on the timestamps anymore.
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!