Re: [Python-3000] Compiling Python 3.0 with VS 2008 Beta2

2007-11-17 Thread Martin v. Löwis
> What combinations of configuration and platform do we need? The migrated > solution has Release, Debug, ReleaseAMD64 and ReleaseItanium as > configurations and Win32 as platform. The platform X64 isn't listed but > I could add it. > > Do we need a ReleaseAMD64 when we could use the platform X64?

Re: [Python-3000] Compiling Python 3.0 with VS 2008 Beta2

2007-11-17 Thread Christian Heimes
Joe Smith wrote: > While ml.exe is intentionally omitted for the express version of Visual C++, > the standard versions of Visual Studio are supposed to include ml.exe. > The VS 2008 beta 2 version omitted it by mistake. At the moment there is no > convenient way to get the latest version. This s

Re: [Python-3000] Compiling Python 3.0 with VS 2008 Beta2

2007-11-17 Thread Christian Heimes
Martin v. Löwis wrote: > The "platform" feature didn't exist in VS 2003 (atleast you couldn't > define new platforms), hence those projects made new configurations. > > In the future, I think we should have only Release and Debug > configurations, and x86 and x64 platforms, and these in all four >

Re: [Python-3000] Compiling Python 3.0 with VS 2008 Beta2

2007-11-17 Thread Martin v. Löwis
>> In the future, I think we should have only Release and Debug >> configurations, and x86 and x64 platforms, and these in all four >> combinations. > > I've tested VS 2008 Beta 2 Express and Standard Edition. I had to > uninstall the Express Edition in order to test the Standard Edition. As > far

Re: [Python-3000] Compiling Python 3.0 with VS 2008 Beta2

2007-11-17 Thread Martin v. Löwis
> Oh, it's an interesting speed up trick. How was the address table > generated. Lucky guessing and gut feeling? :] There is also rebase.exe (resp. editbin /rebase), which may have been used to produce the initial version of this table. Regards, Martin

Re: [Python-3000] Please re-add __cmp__ to python 3000

2007-11-17 Thread Martin v. Löwis
> It'd be simpler still if we only had __cmp__ and __eq__. I just don't > understand the use cases where that's not sufficient. > > Hrm. I guess set's subset checking requires more relationships than > __cmp__ provides. Abandoning that feature probably isn't an option, > so nevermind me. > > (

Re: [Python-3000] Compiling Python 3.0 with VS 2008 Beta2

2007-11-17 Thread Christian Heimes
Update -- The new PCbuild9 directory works for x86. I'm unable to test it for AMD64. The structure is going to change from a ReleaseAMD64 solution towards x86 platform in the future. I've also hacked together a small fix for the msvccompiler module. It's available at http://bugs.python.org/is

Re: [Python-3000] Please re-add __cmp__ to python 3000

2007-11-17 Thread Greg Ewing
Martin v. Löwis wrote: > or __cmp__ would > have to be extended to support "unordered" as a result. That's what I think should be done. -- Greg ___ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsub

[Python-3000] leaking sockets again

2007-11-17 Thread Bill Janssen
I notice that we are leaking sockets again. I believe this is due to the fact that the __del__ methods on socket.socket was removed from the patch I sent in for socket.py. I'll poke further. Bill ___ Python-3000 mailing list Python-3000@python.org htt

Re: [Python-3000] leaking sockets again

2007-11-17 Thread Bill Janssen
> I notice that we are leaking sockets again. I believe this is due to > the fact that the __del__ methods on socket.socket was removed from the > patch I sent in for socket.py. I'll poke further. Nope, that's not it. I'll have to poke at it a bit more. Bill ___