Denis Barbier wrote:
> I called 'python2.6 setup.py install --user' which installs modules
> under $HOME/.local/lib/python2.6/, this is exactly what I want to
> achieve, being able to install as a normal user. This quoted text
> does not mention that, thus I tried 'sudo python2.6 setup.py install'
On 2010/5/21 Thomas Paviot wrote:
> 2010/5/21 Denis Barbier wrote:
[...]
>> Have a look at src/addons/Display/wxDisplay.py for instance:
>> def InitDriver(self):
>> try:
>> os.environ["CSF_GraphicShr"]
>> except KeyError:
>> raise "Please set the CSF_GraphicSh
2010/5/21 Denis Barbier
> On 2010/5/21 Thomas Paviot wrote:
> [...]
> > I had a discussion a couple of days weeks ago with Olider Borm, who
> > contributed the debian binary package for pythonOCC-0.4. It seems not
> > possible to set the CS_GraphicShr variable from the debian packaging
> tool.
>
On 2010/5/21 Thomas Paviot wrote:
[...]
> I had a discussion a couple of days weeks ago with Olider Borm, who
> contributed the debian binary package for pythonOCC-0.4. It seems not
> possible to set the CS_GraphicShr variable from the debian packaging tool.
> So here is his suggestion:
> """
> If
2010/5/21 Denis Barbier
> On 2010/5/21 Thomas Paviot wrote:
> [...]
> > Hi guys,
> > Thanks for your feedbacks with building/installing debian unstable
> > pythonOCC. In order to sum up your experiments, is there something I
> should
> > add to the README file (which is about to be renamed as IN
On 2010/5/21 Thomas Paviot wrote:
[...]
> Hi guys,
> Thanks for your feedbacks with building/installing debian unstable
> pythonOCC. In order to sum up your experiments, is there something I should
> add to the README file (which is about to be renamed as INSALL) for debian
> users?
No, README fi
2010/5/21 Denis Barbier
> On 2010/5/21 John Griessen wrote:
> > Denis Barbier wrote:
> >> I have some trouble with python 2.6, it seems that extensions are not
> >> loaded, no idea why yet.
> >
> > This excerpt from debian policy,
> > http://www.debian.org/doc/packaging-manuals/python-policy/ch-p
On 2010/5/21 John Griessen wrote:
> Denis Barbier wrote:
>> I have some trouble with python 2.6, it seems that extensions are not
>> loaded, no idea why yet.
>
> This excerpt from debian policy,
> http://www.debian.org/doc/packaging-manuals/python-policy/ch-python.html,
> seems complicated and has
Denis Barbier wrote:
> I have some trouble with python 2.6, it seems that extensions are not
> loaded, no idea why yet.
This excerpt from debian policy,
http://www.debian.org/doc/packaging-manuals/python-policy/ch-python.html,
seems complicated and has to do with it:
"Directories with private Pyt
2010/5/20 Denis Barbier
> On 2010/5/14 John Griessen wrote:
> [...]
> > running build_ext
> > building 'OCC._Standard' extension
> > swigging
> /backups-650mb/pythonocc-read-only/src/wrapper/SWIG/linux_darwin/Standard.i
> to
> >
> /backups-650mb/pythonocc-read-only/src/wrapper/SWIG/linux_darwin/S
On 2010/5/14 John Griessen wrote:
[...]
> running build_ext
> building 'OCC._Standard' extension
> swigging
> /backups-650mb/pythonocc-read-only/src/wrapper/SWIG/linux_darwin/Standard.i to
> /backups-650mb/pythonocc-read-only/src/wrapper/SWIG/linux_darwin/Standard_wrap.cpp
> swig -python -O -c++ -
Thomas Paviot wrote:
> Hi John,
>
> I'm not sure the -classic and/or -nomodernargs can be safely used with
> SWIG and python2.6.
Do you want to be able to run with python2.6?
I'm going to start learning pythonocc with 2.5, but wanted to use the
leo editor with ipython and so get into a dependen
Hi John,
I'm not sure the -classic and/or -nomodernargs can be safely used with SWIG
and python2.6.
Thomas
2010/5/18 John Griessen
> John Griessen wrote:
> > I'm still unable to compile with python2.6, but python2.5 goes right past
> this problem.
>
> Any ideas?
>
> With python2.6 doing
> pyth
John Griessen wrote:
> I'm still unable to compile with python2.6, but python2.5 goes right past
> this problem.
Any ideas?
With python2.6 doing
python setup.py build -f
I get this:
.
> .
> .
> running build_ext
> building 'OCC._Standard' extension
> swigging
> /backups-650mb/pythonocc-read-onl
I'm new at cmake and cmake-gui. What should the build dir be set to for GEOM
and SMESH
when running cmake-gui?
John
___
Pythonocc-users mailing list
Pythonocc-users@gna.org
https://mail.gna.org/listinfo/pythonocc-users
I'm still unable to compile. This started when I changed python to 2.6.
Any ideas how to get around this?
Only use python2.5?
John
Thomas Paviot wrote:
> Hi John,
>
> SWIG parameters are defined in the ./src/wrapper/environment.py sciprt.
.
.
>
> python set
Thomas Paviot wrote:
> Hi John,
>
> SWIG parameters are defined in the ./src/wrapper/environment.py sciprt.
.
.
>
> python setup.py build -f
Now I get this:
j...@toolbench:/backups-650mb/pythonocc-read-only/src$ python setup.py build -f
Building pythonOCC-0.5dev for linux2
Checking OCC Standa
17 matches
Mail list logo
