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 arigo
Recipients arigo
Date 2016-12-06.11:51:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1481025068.61.0.497625321202.issue28883@psf.upfronthosting.co.za>
In-reply-to
Content
(C3) _PyGen_yf() checks the opcode at [f_lasti + 1], which is the next
  opcode that will run when we resume the generator: either it is the
  opcode following the YIELD, or it is exactly YIELD_FROM.  It is not
  possible at the moment to write Python code that compiles to a YIELD
  immediately followed by YIELD_FROM, so by chance the two cases are
  correctly distinguished.  *However,* the discussion so far assumes
  that the generator is not currently running.  If it is (which probably
  doesn't occur in reasonable Python code but can be constructed
  manually), then this checks for example the byte/word that describes
  the argument of the currently running opcode.  If we're very unlucky
  this byte has the value 72, which is YIELD_FROM.  Total nonsense and
  crashes follow.
History
Date User Action Args
2016-12-06 11:51:08arigosetrecipients: + arigo
2016-12-06 11:51:08arigosetmessageid: <1481025068.61.0.497625321202.issue28883@psf.upfronthosting.co.za>
2016-12-06 11:51:08arigolinkissue28883 messages
2016-12-06 11:51:08arigocreate