it's about week since RC3 has been released. It would be nice to
release final 6.4.2 within next few days. We have still one blocker
[1] which is hopefully solved. Anything else need to be solved before
releasing (only urgent issues which have some probability that someone
will fix them)?
it's about week since RC3 has been released. It would be nice to
release final 6.4.2 within next few days. We have still one blocker
I would suggest to postpone final release for few days due to recently
introduced switch from Python 2.5 to 2.7 in OSGeo4W framework.
I would raise discussion about releasing 6.4.2. No blockers reported
[1], no other critical bug reported related to py2.7. I would vote for
releasing 6.4.2 in few next days.
I would suggest to postpone final release for few days due to recently
introduced switch from Python 2.5 to 2.7 in OSGeo4W framework.
I would raise discussion about releasing 6.4.2. No blockers reported
[1], no other critical bug reported related to py2.7. I would vote for
releasing 6.4.2 in few next days.
tested a lot wingrass here on my winvista32-box with python 2.7., works
quite nicely and a lot faster than with python 2.5.
everything seems to be working here as well, except for a small issue just found by a student in wingrass
and confirmed in freshly compiled release on mac:
On Feb 4, 2012, at 4:32 PM, Helmut Kudrnovsky wrote:
I would suggest to postpone final release for few days due to recently
introduced switch from Python 2.5 to 2.7 in OSGeo4W framework.
I would raise discussion about releasing 6.4.2. No blockers reported
[1], no other critical bug reported related to py2.7. I would vote for
releasing 6.4.2 in few next days.
tested a lot wingrass here on my winvista32-box with python 2.7., works
quite nicely and a lot faster than with python 2.5.
everything seems to be working here as well, except for a small issue just found by a student in wingrass
and confirmed in freshly compiled release on mac:
However, there never seems to have been a bug report about this.
right it's quite know issue, but not reported AFAIR. I would assume
that it's probable to fix it for 6.4.3 (different wxGUI code base). In
other words it's not blocker for 6.4.2.