Message 200388 - Python tracker

➜

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	lemburg
Recipients	eric.araujo, ezio.melotti, fredericaltorres, lemburg, numerodix
Date	2013年10月19日.08:36:40
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<52624490.1000206@egenix.com>
In-reply-to	<1382159181.93.0.139770689129.issue8964@psf.upfronthosting.co.za>

Content
On 19.10.2013 07:06, Martin Matusiak wrote: > > Martin Matusiak added the comment: > > It seems the versions of IronPython 1.0 mentioned in test cases do actually support the "in" keyword, so the first version of the patch is probably sufficient. > > Example session: > >>>> sys.version > IronPython 1.0.60816 on .NET 2.0.50727.3643 >>>> "IronPython" in sys.version > True >>>> sys.version.startswith("IronPython") > True In that case, I'm +1 on using both to clean up the code.

Content

On 19.10.2013 07:06, Martin Matusiak wrote:
> 
> Martin Matusiak added the comment:
> 
> It seems the versions of IronPython 1.0 mentioned in test cases do actually support the "in" keyword, so the first version of the patch is probably sufficient.
> 
> Example session:
> 
>>>> sys.version
> IronPython 1.0.60816 on .NET 2.0.50727.3643
>>>> "IronPython" in sys.version
> True
>>>> sys.version.startswith("IronPython")
> True
In that case, I'm +1 on using both to clean up the code.

History
Date	User	Action	Args
2013年10月19日 08:36:40	lemburg	set	recipients: + lemburg, ezio.melotti, eric.araujo, fredericaltorres, numerodix
2013年10月19日 08:36:40	lemburg	link	issue8964 messages
2013年10月19日 08:36:40	lemburg	create

homepage