On Mon, Nov 17, 2014 at 2:22 PM, Greg email@example.com wrote:
On 17/11/2014 2:29 p.m., Chris Angelico wrote:
barry_as_FLUFL: Not entirely sure what this one actually accomplishes. :)
It determines whether "not equal" is spelled "!=" or "<>", so it fits the pattern of being compile-time-only.
Right. So, are there any __future__ directives that have any effect on byte-code? I'm not seeing any, though that may just mean I didn't recognize one.