Re: Regression in build 1964, AddGrowableCol fails
Eric Fahlgren <[email protected]>
| Newsgroups | gmane.comp.python.wxpython.devel |
|---|---|
| Message-ID | <CAP2Qz+V=2tqHTztKMN6ZVb90ryOyJBKuEF2-weNgufk5sJM0eQ@mail.gmail.com> |
Aha, I did find the "VC for Python" 9.0 compiler, thanks a bunch! The 3.5 port isn't going to happen soon for us: 40k lines of gui code dependent on wxPython and another 30k lines or so with VTK dependencies that will need an as-yet unknown amount of work... The other 130k lines of "pure python" is already pretty much ready to go, except for the bytes/str nightmare I'm sure we'll encounter... Thanks again for the pointer to that 9.0 compiler. On Tue, Apr 19, 2016 at 3:22 PM, Chris Barker <[email protected]> wrote: > On Mon, Apr 18, 2016 at 6:52 PM, Eric Fahlgren <[email protected]> > wrote: > >> Yeah, in an ideal world I'd use VC++ 9.0, but we can't get it any more >> > > that's what that "new" link is for -- MS actually created and posted a > version specifically to support Python2.7 -- just for these reasons. > > >> and we've been building other stuff like vtk with 10.0 for about six >> years without issue. I suspect it's mostly in the IO libraries that things >> go to dll hell, so when I try to do wxPrintf or whatever it is hit or miss. >> > > yup -- that's the killer one -- but if it's working for you, it's working > for you. > > >> For our production code we use classic wxPython, with the release >> installers, so everything there is kosher, but I'm currently working on >> trying to make Phoenix work (as part of our migration to Py3), so I've just >> started to build my own wxPython bundle for testing and porting. >> > > hopefully you can go straight to py3.5 and VS2015 in that case. > > >> As an aside, I can't see CPython 2.7 staying with the ancient Windows >> compiler until end-of-life in 2020, since hardware is going to fail and the >> licenses on those old boxes will be lost and pretty soon there won't be any >> build machines for it... >> > > I wouldn't be so sure -- as I said there is a compiler MS has made > available -- and the core dev team REALLY doesn't want to create an > incompatible build, now a new version simiply for a new Windows Compiler... > > >> That's one of the, oh, billion or so reasons I'm pushing on Py3 >> compatibility right now. >> > > yeah -- it's time. > > -Chris > > > -- > > Christopher Barker, Ph.D. > Oceanographer > > Emergency Response Division > NOAA/NOS/OR&R (206) 526-6959 voice > 7600 Sand Point Way NE (206) 526-6329 fax > Seattle, WA 98115 (206) 526-6317 main reception > > [email protected] > > -- > 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. > -- 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.