[IronPython] unchanged version numbers (was Re: Announcing IronPython 2.0.1)

John Machin sjmachin at lexicon.net
Tue Mar 10 05:10:14 CET 2009

On 14/02/2009 9:39 AM, Dino Viehland wrote:
> It’s an in-place upgrade so you don’t need to re-build hosts that were 
> built against the previous versions of IronPython – they’ll just 
> continue to work.  If we changed the .NET assembly version then you’d 
> either have to apply policy or rebuild.  The assembly file version is 
> updated and that’s how you can distinguish the two builds.
> *From:* users-bounces at lists.ironpython.com 
> [mailto:users-bounces at lists.ironpython.com] *On Behalf Of *Marty Nelson
> *Sent:* Friday, February 13, 2009 2:32 PM
> *To:* Discussion of IronPython
> *Subject:* Re: [IronPython] Announcing IronPython 2.0.1
> Why is the assembly version the same as 2.0?

But the output of sys.version and sys.version_info doesn't appear to 
change either ... why not? and what is there that does change that apps 
can access as easily as sys.version_info and  put it out on a logfile so 
that support people know exactly what binary is being run?

More information about the Ironpython-users mailing list