> Are you suggesting creating vs10to9, which would be congruent to vs9to8, or
> vs9to10?
After reconsidering, I don't think I want anything like this in the tree
at this point. The code will be outdated by the time Python 3.3 is
released, as Python 3.3 will be built with a Visual Studio different
> From: python-dev-bounces+jaraco=jaraco@python.org [mailto:python-
> dev-bounces+jaraco=jaraco@python.org] On Behalf Of Jason R. Coombs
> Sent: Monday, 16 January, 2012 19:01
>
> I'm unsure if the conversion from 9 to 10 or 10 to 9 can be as simple as
the
> vs9to8 suggests. When I run the
On Mon, Jan 16, 2012 at 18:01, Jason R. Coombs
> My goal in adding the upgrade code was to provide a one-step upgrade for
> developers with only VS 10 installed. That's what vs-upgrade in
> jaraco.develop does.
Upgrading to 2010 requires some code changes in addition to the
conversion, so the proc
> From: "Martin v. Löwis" [mailto:mar...@v.loewis.de]
> Sent: Monday, 16 January, 2012 16:25
>
> I'd be hesitant to put too many specialized tools into the tree that will
> become unmaintained. Please take a look at the vs9to8 tool in PCbuild; if
you
> could adjust that to support VS 10, it would b
> If there are no objections, I’ll work to extract the aforementioned
> functionality from the jaraco.develop modules and into a portable script
> and put together a proof-of-concept in the default branch. The build
> script should not interfere with any build bots or other existing build
> process
> From: Brian Curtin [mailto:br...@python.org]
> Sent: Monday, 16 January, 2012 15:20
>
> 2010 is adequate for limited use but the test suite doesn't pass, so I
would be
> hesitant to add support and/or documentation for building with it until we
> actually support it the same as or in place of 200
On Mon, Jan 16, 2012 at 14:00, Jason R. Coombs wrote:
> The second thing I notice is the scripts assume Visual Studio 2008. And
> while I recognize that Python is specifically built against Visual Studio
> 2008 for the official releases and that Visual Studio 2008 may be the only
> officially-supp
The current scripts for building Python lack some things to be desired.
The first thing I notice when I try to build Python on Windows is the
scripts expect to be run inside of a Visual Studio environment, the
environment of which is only defined inside of a cmd.exe context. This means
the scri
