[tahoe-lafs-trac-stream] [pycryptopp] #65: alleged bug in SHA256 on win32 MSVC 2005 release build

[pycryptopp]

#65: alleged bug in SHA256 on win32 MSVC 2005 release build
-------------------+-------------------------
Reporter:  zooko   |          Owner:
    Type:  defect  |         Status:  closed
Priority:  major   |      Milestone:  0.6.0
 Version:  0.5.19  |     Resolution:  invalid
Keywords:          |  Launchpad Bug:
-------------------+-------------------------
Changes (by zooko):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 Hm, I'll bet this bug happens only with a specific version of the MSVC
 compiler, and that Python (and hence all Python modules such as
 pycryptopp) require a different specific version. Official CPython 2.6 and
 2.7 for Windows is built, I think, with Visual Studio 2008. Presumably
 that compiler doesn't have this bug, which explains why we never see it on
 our buildbots or hear reports of it from our users.

 Our MSVC buildbot https://tahoe-lafs.org/buildbot-
 pycryptopp/builders/Dcoder%20Win7-64%20py2.6/builds/19/steps/show-tool-
 versions/logs/stdio reports its {{{cl}}} version as:

 {{{
 cl: Microsoft (R) C/C++ Optimizing Compiler Version 15.00.30729.01 for x64
 Copyright (C) Microsoft Corporation.  All rights reserved.
 }}}

 According to http://msdn.microsoft.com/en-
 us/library/bb384838%28v=VS.90%29.aspx that indicates that it is Visual
 Studio 2008.

 Closing this ticket as {{{invalid}}}.

-- 
Ticket URL: <http://tahoe-lafs.org/trac/pycryptopp/ticket/65#comment:8>
pycryptopp <https://tahoe-lafs.org/trac/pycryptopp>