This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author steve.dower
Recipients BreamoreBoy, steve.dower, tim.golden, zach.ware
Date 2015-02-12.01:10:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1423703448.01.0.678513139027.issue23450@psf.upfronthosting.co.za>
In-reply-to
Content
These are warnings about implicit downcasting in a 64-bit build. They're not fatal to the build or execution (as far as we know), and as nice as it would be to fix them all, "good" fixes may introduce behaviour changes (for example, new overflow errors).

As an aside, building with VS 2015 also shows a lot of warnings for variable shadowing, which should also be fixed but is not likely unless someone gets really annoyed by them. What's the usual policy on issues like this?
History
Date User Action Args
2015-02-12 01:10:48steve.dowersetrecipients: + steve.dower, tim.golden, BreamoreBoy, zach.ware
2015-02-12 01:10:48steve.dowersetmessageid: <1423703448.01.0.678513139027.issue23450@psf.upfronthosting.co.za>
2015-02-12 01:10:47steve.dowerlinkissue23450 messages
2015-02-12 01:10:47steve.dowercreate