Closed GoogleCodeExporter closed 9 years ago
I have done some refactoring but have not yet updated the install script... You
can always run visvis by just placing it somewhere on your PYTHONPATH.
Original comment by almar.klein@gmail.com
on 13 Aug 2012 at 8:31
It's far from ideal...
Here is the modified packages list:
packages = ['visvis',
'visvis.functions',
'visvis.backends',
'visvis.processing',
'visvis.vvmovie',
'visvis.io',
'visvis.utils',
'visvis.utils.ssdf',
'visvis.text',
'visvis.text.freetype',
'visvis.core',
'visvis.wibjects',
'visvis.wobjects'],
I also had problem with import ".xxx" syntax. I think it's far better to
specify the whole path:
visvis/text/__init__.py:
from visvis.text.text_base import AtlasTexture, FontManager, BaseText
from visvis.text.text_base import Text, Label
from visvis.text.text_prerendered import PrerenderedFontManager
visvis/text/text_freetype.py:
from visvis.core.misc import getResourceDir, getOpenGlCapable
import subprocess
from visvis.core.shaders import Shader, ShaderCodePart
from visvis.text.text_base import AtlasTexture, FontManager, Text, Label
from visvis.text.text_base import correctVertices, simpleTextureDraw
from visvis.text.freetype import ( Face, Vector, Matrix, FT_KERNING_UNFITTED,
FT_LOAD_RENDER, FT_LOAD_FORCE_AUTOHINT )
Nicolas
Original comment by Nicolas.Rougier@gmail.com
on 13 Aug 2012 at 8:43
What kind of problems did you have?
I changed it to absolute. But there is some code elsewhere in visvis where
relative imports are used and hard to remove. Let me know if you still have
problems...
Original comment by almar.klein@gmail.com
on 16 Aug 2012 at 2:35
Original issue reported on code.google.com by
Nicolas.Rougier@gmail.com
on 13 Aug 2012 at 8:26