On Wed, 8 Jun 2005, James Graham wrote:
Jeremy Sanders wrote:
On Tue, 7 Jun 2005, James Graham wrote:
It might well be because the __init__.py files don't define __all__ which
AFAIK is needed for locating modules in Windows. If so this should be
trivial to fix.
Didn't know they needed __
Jeremy Sanders wrote:
On Tue, 7 Jun 2005, James Graham wrote:
It might well be because the __init__.py files don't define __all__
which AFAIK is needed for locating modules in Windows. If so this
should be trivial to fix.
Didn't know they needed __all__...
Actually it looks like you only
On Tue, 7 Jun 2005, James Graham wrote:
It might well be because the __init__.py files don't define __all__ which
AFAIK is needed for locating modules in Windows. If so this should be trivial
to fix.
Didn't know they needed __all__...
Jeremy
--
Jeremy Sanders <[EMAIL PROTECTED]>
http://www.
Jamie C wrote:
I dealt with the issue where you do "import directory.pythonfile" by
just putting everything in the same directory and changing it to
"import pythonfile"
That should work, no? Why do you need the hack?
Well, I dunno why this is, but just running veusz.py gives the er
> > settingdb gives an exception on close, but other than that and the
> > weird bug where the graph is postage-stamp sized
>
> That's probably because it can't find the geometry settings.
Makes sense.
> I've had a look at moving SettingsDb to QSettings and it seems pretty
> easy... Well I can ge
On Tue, 31 May 2005, Jamie C wrote:
http://www-xray.ast.cam.ac.uk/~jc/veusz.png
Cool!
settingdb gives an exception on close, but other than that and the
weird bug where the graph is postage-stamp sized
That's probably because it can't find the geometry settings.
I've had a look at moving
http://www-xray.ast.cam.ac.uk/~jc/veusz.png
settingdb gives an exception on close, but other than that and the
weird bug where the graph is postage-stamp sized it seems to pretty
much work.
I dealt with the issue where you do "import directory.pythonfile" by
just putting everything in the same dir
