➜

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 dangyogi
Recipients amaury.forgeotdarc, dangyogi, hagen, kcarnold
Date 2010-05-03.17:51:52
SpamBayes Score 6.0019454e-05
Marked as misclassified No
Message-id <1272909114.58.0.832205017278.issue4806@psf.upfronthosting.co.za>
In-reply-to
Content 
I have also hit this error.  I went to report it but found it already entered (good news), but not resolved from nearly a year ago (bad news).

The error masked another bug that I had in my program and it took me quite awhile to figure out what the real problem was.

I use *generator arguments quite a lot, so was surprised to see the error.  So I, for one, can say that if you disable *generator arguments, you will break existing code.

If anybody cares, I have verified that this error also appears in Python2.5 and Python2.4 and am attempting to add python2.5 to the Versions list.  (And yes, *generators were allowed in Python2.4!)

Is this headed for resolution?  Progress on it seems to have stalled nearly a year ago.  Can I vote to revive this?
History
Date User Action Args
2010-05-03 17:51:54dangyogisetrecipients: + dangyogi, amaury.forgeotdarc, hagen, kcarnold
2010-05-03 17:51:54dangyogisetmessageid: <1272909114.58.0.832205017278.issue4806@psf.upfronthosting.co.za>
2010-05-03 17:51:53dangyogilinkissue4806 messages
2010-05-03 17:51:52dangyogicreate