>Ok. May I suggest not including sample updates in IronPython release
>notes if they have their own release cycle... :-)
Yes my fault there. I didn't know about the separate release cycle for samples. 
I'm learning... :)

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Foord
Sent: Thursday, August 07, 2008 10:16 AM
To: Discussion of IronPython
Subject: Re: [IronPython] pyc.py sample

Dave Fugate wrote:
> Hi Michael, this seems like as good of a time as any to shed some light on 
> our thoughts around the IronPython samples.  First Pyc - Pyc.py was indeed 
> updated for IronPython 2.x in our internal TFS repository last month, but as 
> most people are already aware we don't reship the samples with every minor 
> release of IronPython.  The main reason we do this (at least from my 
> perspective) is testing.  Most of the samples are GUI-based and need to be 
> tested by hand which is quite time consuming.

Testing GUI applications - particularly windows forms based ones - is a
process amenable to automation. We have a few hundred automated
'functional tests' for Resolver One and I can highly recommend it.

>  By cutting the samples out of minor IronPython releases, we're able to 
> release IronPython in quicker intervals and focus more test time on new 
> features as opposed to samples verification.  Regardless, we believe this 
> sample depicts a vital aspect of IronPython functionality and will do a 
> one-time 2.0B4 release of Pyc on www.codeplex.com/IronPython sometime today 
> to get feedback.
>
> As for inclusion of the samples into the installer for IronPython 2.0, our 
> current plan is actually to follow what we did with IronPython 1.0.  That is, 
> we'll release the samples shortly after 2.0 ships.  The fundamental reason 
> for doing this is that delaying samples work lets us put more effort into 
> improving the quality of ipy.exe and the core IronPython documentation.
>
Ok. May I suggest not including sample updates in IronPython release
notes if they have their own release cycle... :-)

Michael


> Dave
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Foord
> Sent: Thursday, August 07, 2008 5:52 AM
> To: Discussion of IronPython
> Subject: [IronPython] pyc.py sample
>
> Hello guys,
>
> The IronPython 2.0b4 release notes state:
>
> # Static compilation of python files is now supported again and the pyc.py
> sample has been updated to use the newer version.
>
> Where is the updated sample? I can't find it...
>
> As samples are updated for IronPython 2 it would make sense to move them
> into the installer (in their own directory on the start menu entry for
> IronPython).
>
> Michael
>
> --
> http://www.ironpythoninaction.com/
> http://www.voidspace.org.uk/
> http://www.trypython.org/
> http://www.ironpython.info/
> http://www.resolverhacks.net/
> http://www.theotherdelia.co.uk/
>
> _______________________________________________
> Users mailing list
> [email protected]
> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>
> _______________________________________________
> Users mailing list
> [email protected]
> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>


--
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/
http://www.trypython.org/
http://www.ironpython.info/
http://www.resolverhacks.net/
http://wwww.theotherdelia.co.uk/

_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com

_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com

Reply via email to