Am 21.10.12 21:52, schrieb Christian Heimes:
Ultimately it's your decision. You are the expert and build master for
Windows releases. I've no hard feelings if you prefer to include the
code in the main dll. Just say so and I will change the module ASAP.
It doesn't really matter much either way
Am 21.10.2012 21:27, schrieb "Martin v. Löwis":
> It's a packaging and maintenance issue. If it is in pythonxy.dll, the
> project file becomes easier to maintain. That's why I was always opposed
> to splitting up the existing pythonxy.dll into many project files.
>
> OTOH, when adding a module, a
On Sun, 21 Oct 2012 21:31:02 +0200
Christian Heimes wrote:
> Am 21.10.2012 20:53, schrieb Antoine Pitrou:
> > I don't know. If it breaks VS 2010 then it should be reverted. On the
> > other hand I'd like to continue building Python under Windows without
> > needing to install yet another MSVC vers
Am 21.10.2012 20:53, schrieb Antoine Pitrou:
> I don't know. If it breaks VS 2010 then it should be reverted. On the
> other hand I'd like to continue building Python under Windows without
> needing to install yet another MSVC version.
I backed out your commit and committed a _sha3.vcproj file ins
On Sun, 21 Oct 2012 17:32:02 +0200
Christian Heimes wrote:
> Am 21.10.2012 17:23, schrieb antoine.pitrou:
> > http://hg.python.org/cpython/rev/ce9c9cbd1b11
> > changeset: 79875:ce9c9cbd1b11
> > user:Antoine Pitrou
> > date:Sun Oct 21 17:21:04 2012 +0200
> > summary:
> > Build
Am 21.10.2012 17:23, schrieb antoine.pitrou:
> http://hg.python.org/cpython/rev/ce9c9cbd1b11
> changeset: 79875:ce9c9cbd1b11
> user:Antoine Pitrou
> date:Sun Oct 21 17:21:04 2012 +0200
> summary:
> Build the _sha3 module with VS 2008.
For VS 2010 I decided against this approac
