Repository navigation
Conversation
|
I think the reason for the wxversion requirement was that people were running into trouble when they had two versions installed; maybe they had 2.6 and 2.8, and the 2.6 was getting imported. Why is it so onerous to require wxversion? |
|
You're right, it's not terribly onerous. Indeed, wxPython defaults to building wxversion. Perhaps my package manager (homebrew) simply made a poor choice in choosing to override this. As a novice, it took me quite a bit of time to determine the problem here. In doing so, I found a stackoverflow question where the poster had similar issues. Add in the fact that the obvious ways to extend the python path ( |
|
I'm going to close this and merge #886. An alternative would be to simply warn if wxversion is not present; if discussion indicates that is a good idea, then it can be advanced as a pull request to master. |
It seems silly to me to have wxversion as a hard dependency when it's not a requirement for a proper installation of wx. Especially so since backend_wx.py still checks the
VERSION_STRINGafter using going through all the hoops with wxversion. This is simply an alternative.