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 ghazel
Recipients ghazel, terry.reedy
Date 2010-06-10.00:14:21
SpamBayes Score 0.012652849
Marked as misclassified No
Message-id <1276128864.16.0.537137296814.issue3423@psf.upfronthosting.co.za>
In-reply-to
Content
Searching the file for "raise" is sort of pointless, since exec() takes a string which might have come from anywhere, and there might be any number of exec() calls in the module. See: http://codepad.org/7EBMhb0O

There are at least two reasonable answers:

<string>:1: DeprecationWarning: raising a string exception is deprecated
  raise 'two'

or:

t.py:7: DeprecationWarning: raising a string exception is deprecated
  exec(x)

Either one would be fine, but randomly choosing the first line of the module where exec() is called is just nonsense.

If you want one that applies to Python 3.x, here you go: http://codepad.org/Mq1eZyoE
History
Date User Action Args
2010-06-10 00:14:24ghazelsetrecipients: + ghazel, terry.reedy
2010-06-10 00:14:24ghazelsetmessageid: <1276128864.16.0.537137296814.issue3423@psf.upfronthosting.co.za>
2010-06-10 00:14:22ghazellinkissue3423 messages
2010-06-10 00:14:21ghazelcreate