Re: Regression in build 1964, AddGrowableCol fails
Eric Fahlgren <[email protected]>
| Newsgroups | gmane.comp.python.wxpython.devel |
|---|---|
| Message-ID | <CAP2Qz+U84WL0NB+n6DsUnwuB_Z-uj82v3YU_VCpMD+UX_2-3oA@mail.gmail.com> |
Hi Chris, Yeah, in an ideal world I'd use VC++ 9.0, but we can't get it any more 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. 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. I'll go back to the snapshot builds as soon as Scott's PRs get merged into the build and I can move on to finding other bugs. 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... That's one of the, oh, billion or so reasons I'm pushing on Py3 compatibility right now. Eric On Mon, Apr 18, 2016 at 8:41 AM, Chris Barker - NOAA Federal < [email protected]> wrote: > > > (albeit with a hack to distutils to use VC > > 10.0 instead of 9.0, which may be sending > > me to dll hell, but whatever -- > > You really don't want to do that with py2.7. Does the "Microsoft complied > for Python" not work for you? > > https://www.microsoft.com/EN-US/windows/windows-10-upgrade > > > > I am seeing various segfaults that I don't think I've seen before). > > That could be due to run time incompatibility -- I wouldn't go too far > with the wrong complier. > > -CHB > > > > > > I'll give it a try and let you know. > > Eric > > > On Fri, Apr 15, 2016 at 6:01 PM, Scott Talbert <[email protected]> wrote: > >> It turns out that this was more complicated than I expected. Do you >> happen to have a dev environment where you could test this patch on Win64? >> I believe it should solve the problems but I don't have a Win environment >> readily available. >> >> Scott >> >> On Wed, 13 Apr 2016, Eric Fahlgren wrote: >> >> On Wed, Apr 13, 2016 at 3:54 PM, Scott Talbert <[email protected]> wrote: >>> And you're using the 64-bit compiled version, right? >>> >>> >>> Oops, forgot to say that... Correct: all 64-bit, all the time. >>> >>> I do a "pip download", check that the version looks correct, then install >>> the local wheel into my venv. >>> >>> wxPython_Phoenix-3.0.3.dev1943+fdf739f-cp27-cp27m-win_amd64.whl >>> wxPython_Phoenix-3.0.3.dev1964+f780b21-cp27-cp27m-win_amd64.whl >>> >>> -- >>> 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. > > -- > 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.