Comment 2 for bug 399106

I am not sure I understand what this is in your sentence. I don't know how
to patch pyreport to work in this situation. Unfortunately I'm a bit lost
in the meta programming required.

On Tue, Jul 14, 2009 at 12:02 AM, Gael Varoquaux <
<email address hidden>> wrote:

> On Tue, Jul 14, 2009 at 03:40:13AM -0000, Joe Coffey wrote:
> > Pyreport seems like a great piece of software. Unfortunately a fair
> > amount of my groups modules are loaded by an importer that prepends:
>
> > from __future__ import division, absolute_import
>
> > before the module. This seems to make using pyreport impossible. Is
> > there anyway out? Removing from future import from the modules isn't an
> > option. I don't have control over the codebase.
>
> Do you want to send a patch adding an option to do this? I totally
> sympathize with your points.
>
> Gaël
>
> --
> from future import ...
> https://bugs.launchpad.net/bugs/399106
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in pyreport: generate reports out of python scripts: New
>
> Bug description:
> Pyreport seems like a great piece of software. Unfortunately a fair amount
> of my groups modules are loaded by an importer that prepends:
>
> from __future__ import division, absolute_import
>
> before the module. This seems to make using pyreport impossible. Is there
> anyway out? Removing from future import from the modules isn't an option. I
> don't have control over the codebase.
>