On Tue, Jun 11, 2013 at 8:27 AM, dhyams <dhy...@gmail.com> wrote: > I guess I'll have to agree to disagree here...the situation I'm in is that I > want a user to be able to write a mathematical plugin with as little effort > as possible. So I want the "from __future__ import division" to be baked > into the plugin, without have to require the user to put that bit of > confusingness at the top of every plugin they write. It's a matter of > elegance to the end-user, especially because I want to make the plugins as > idiot-proof as I can. It will be common for a user not familiar with python > to make the common 1/2 mistake (vs. 1.0/2.0). > > Is that not a reasonable use-case?
Can you read the file into a string, prepend a future directive, and then compile the string? Alternatively, can you switch to Python 3, where the future directive isn't necessary? :) If all else fails, you should be able to just copy and mod the function into your own source file. ChrisA -- http://mail.python.org/mailman/listinfo/python-list
