Thanks for your quick reply. However, this didn't fix it for me:
Basically if I have a file tester.py of the form:
from future import division, absolute_import
print "hi"
Then:
/usr/local/bin/python2.6.1 pyreport.py tester.py
still kicks an error
Traceback (most recent call last):
File "pyreport.py", line 1260, in <module>
commandline_call()
File "pyreport.py", line 1200, in commandline_call
main(pyfile, overrides=options)
File "pyreport.py", line 1256, in main
compiler.compile( output_list, options.outfile, options)
File "pyreport.py", line 959, in compile
html_string = re.sub(r"</style>", protect(cssextra), html_string)
File "pyreport.py", line 583, in protect
return re.sub(r"\\", r"\\\\", string)
File "/u/coffey/localpythonrecent/lib/python2.5/re.py", line 150, in sub
return _compile(pattern, 0).sub(repl, string, count)
TypeError: __call__() takes at most 5 arguments (6 given)
This happens both under pthon 2.5.2 and 2.6.1 (64bit).
On Tue, Jul 14, 2009 at 1:32 PM, Gael Varoquaux <
<email address hidden>> wrote:
> On Tue, Jul 14, 2009 at 11:50:17AM -0000, Joe Coffey wrote:
> > 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.
>
> OK, I have release a new version correcting this: 0.3.3. You can download
> it from pypi:
> http://pypi.python.org/pypi/pyreport
> I have also changed a with details to make it work better on python 2.6.
>
> Hope this helps,
>
> 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.
>
Thanks for your quick reply. However, this didn't fix it for me:
Basically if I have a file tester.py of the form:
from future import division, absolute_import
print "hi"
Then:
/usr/local/ bin/python2. 6.1 pyreport.py tester.py
still kicks an error
Traceback (most recent call last): _call() compile( output_list, options.outfile, options) localpythonrece nt/lib/ python2. 5/re.py" , line 150, in sub
File "pyreport.py", line 1260, in <module>
commandline
File "pyreport.py", line 1200, in commandline_call
main(pyfile, overrides=options)
File "pyreport.py", line 1256, in main
compiler.
File "pyreport.py", line 959, in compile
html_string = re.sub(r"</style>", protect(cssextra), html_string)
File "pyreport.py", line 583, in protect
return re.sub(r"\\", r"\\\\", string)
File "/u/coffey/
return _compile(pattern, 0).sub(repl, string, count)
TypeError: __call__() takes at most 5 arguments (6 given)
This happens both under pthon 2.5.2 and 2.6.1 (64bit).
On Tue, Jul 14, 2009 at 1:32 PM, Gael Varoquaux <
<email address hidden>> wrote:
> On Tue, Jul 14, 2009 at 11:50:17AM -0000, Joe Coffey wrote: pypi.python. org/pypi/ pyreport /bugs.launchpad .net/bugs/ 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.
>
> OK, I have release a new version correcting this: 0.3.3. You can download
> it from pypi:
> http://
> I have also changed a with details to make it work better on python 2.6.
>
> Hope this helps,
>
> Gaël
>
> --
> from future import ...
> https:/
> 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.
>