visualpython-users

[Visualpython-users] Experimental Windows version for Python 2.4

[Bruce S. <Bru...@nc...>]

Now available at vpython.org is an experimental version of VPython for 
Python 2.4 on Windows. The only known bug is that programs that use the 
"text" module to display block letters (including the demo programs 
stonehenge.py and texttest.py) fail on some but not all computers. We 
would appreciate feedback on this or other bugs you may find. This was 
built using the new Boost-based package created by Jonathan Brandmeyer.

Bruce Sherwood

Re: [Visualpython-users] Idle for VPython

[Floris B. <fb...@so...>]

Just for the record.  Last time I mentioned that I might also make
pythonX.Y-visual packages for Debian.  Having had a go at that now I
discovered that will never hapen (and indeed I didn't see any real
benefit from it, but it was a technical challenge) since
libboost-python-dev is only available for the default Debian Python
version (v2.3 currently).  So I also see no need in shipping Idle.

For those who missed the original message, I have a package
python-visual which does install VPython on Debian.  The source
packages should work in sarge and sid, the binary (only i386 for now,
I can provide sparc if there is intrest) package works on sarge and
only _maybe_ on sid (again, if there is intrest I can provide them for
sid as well with pbuilder).  You can get them from
http://www.soton.ac.uk/~fb102/Debian/

For those checking that place again, there is no need to upgrade to
the 3.0.3-2 version as the package is unchanged.  Only the build
process (debian/rules) is changed a little.

Cheers
Floris


On Wed, Dec 22, 2004 at 05:51:50PM -0500, Jonathan Brandmeyer wrote:
> 
> Since Python 2.3 was released, we have not been installing Idle for
> VPython except for systems using Python 2.2.  If anyone is still using
> Python 2.2 and needs us to continue shipping Idle for VPython in the
> source package, please speak up.  Otherwise, it will not be shipped in
> future source packages.
> 
> Thanks,
> -Jonathan
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now. 
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users

-- 
Debian GNU/Linux -- The power of freedom
www.debian.org | www.gnu.org | www.kernel.org

[Visualpython-users] CVS changes

[Jonathan B. <jbr...@ea...>]

This is just a heads-up for anyone who is working from our CVS
repository.

VPython's CVS repository has recently undergone a major layout change.
There is a new module, named "vpython", which includes the source from
the various independent modules that have been used to construct
VPython.  The CVSROOT remains
cvs.sourceforge.net:/cvsroot/visualpython.  

The primary reason for doing this was to have a clean way of placing all
of the build support scripts under version control, which makes it
easier to deterministically produce new source releases.  The directory
layout of the new module is identical to the layout in future source
packages, and nearly the same as past source packages.  The
documentation has also been placed under version control in the new
module.  The old modules remain in order to preserve their history.  The
next release will be produced from the new CVS module.

The work on the next major revision of Visual will remain in the
vpython-core2 module.

-Jonathan Brandmeyer

[Visualpython-users] CVS changes

[Jonathan B. <jdb...@un...>]

This is just a heads-up for anyone who is working from our CVS
repository.

VPython's CVS repository has recently undergone a major layout change.
There is a new module, named "vpython", which includes the source from
the various independent modules that have been used to construct
VPython.  The CVSROOT remains
cvs.sourceforge.net:/cvsroot/visualpython.  

The primary reason for doing this was to have a clean way of placing all
of the build support scripts under version control, which makes it
easier to deterministically produce new source releases.  The directory
layout of the new module is identical to the layout in future source
packages, and nearly the same as past source packages.  The
documentation has also been placed under version control in the new
module.  The old modules remain in order to preserve their history.  The
next release will be produced from the new CVS module.

The work on the next major revision of Visual will remain in the
vpython-core2 module.

-Jonathan Brandmeyer

[Visualpython-users] Idle for VPython

[Jonathan B. <jdb...@un...>]

Since Python 2.3 was released, we have not been installing Idle for
VPython except for systems using Python 2.2.  If anyone is still using
Python 2.2 and needs us to continue shipping Idle for VPython in the
source package, please speak up.  Otherwise, it will not be shipped in
future source packages.

Thanks,
-Jonathan

Re: [Visualpython-users] vpython installing numeric

[Jonathan B. <jbr...@ea...>]

On Fri, 2004-12-17 at 12:41 -0600, cypherpunk1 wrote:
> Hello,
>=20
> =20
>=20
> I want to play with Vpython but I=A2ve been using
> Numeric-23.1.win32-py2.3 with Python 2.3.4.  I=A2ve imported and used
> some of the Numeric 23.1 modules in my other programs therefore I
> don=A2t want to go back to Numeric 23.0.
>=20
> =20
>=20
> According to the instructions at:
>=20
> http://vpython.org/win_download.html
>=20
> =20
>=20
> The installer for Vpython will replace Numeric 23.1 with Numeric
> 23.0. =20
>=20
> Is there anyway to just get an installer for Vpython?
>=20
> I=A2m running Python 2.3.4 and Numeric-23.1 under Windows XP
> Professional.

First off, the version in the installer might actually be more recent
than 23.0.  So, I recommend that you run our installer, and check the
value of Numeric.__version__ (a string).  If it is too low, then delete
C:\Python23\Lib\site-packages\Numeric after installing Visual, and run
the Numeric installation program.

HTH,
-Jonathan

[Visualpython-users] vpython installing numeric

[cypherpunk1 <cyp...@co...>]

Hello,
 
I want to play with Vpython but I've been using Numeric-23.1.win32-py2.3
with Python 2.3.4.  I've imported and used some of the Numeric 23.1
modules in my other programs therefore I don't want to go back to
Numeric 23.0.
 
According to the instructions at:
http://vpython.org/win_download.html
 
The installer for Vpython will replace Numeric 23.1 with Numeric 23.0.  
Is there anyway to just get an installer for Vpython?
I'm running Python 2.3.4 and Numeric-23.1 under Windows XP Professional.


Thanks,
Dillweed

[Visualpython-users] compiling error on suse 9.1

[Giuliano B. <gb...@so...>]

Hi,
I'm trying to install visual python 3.0 on suse 9.1 using gcc 3.3.3
and since my python is under
 >/usr
instead of
 >/usr/local
I used
 >./configure --prefix=/usr
and then
 >make
The result is
 >cvisual.h:8:47: boost/python/detail/wrap_python.hpp: No such file or 
directory
 >cvisual.h:12:34: boost/python/tuple.hpp: No such file or directory
 >cvisual.h:13:33: boost/python/list.hpp: No such file or directory
then I used
 >./configure --prefix=/usr --includedir=/usr/include
and then
 > make
and the result is again
 >cvisual.h:8:47: boost/python/detail/wrap_python.hpp: No such file or 
directory
 >cvisual.h:12:34: boost/python/tuple.hpp: No such file or directory
 >cvisual.h:13:33: boost/python/list.hpp: No such file or directory
So I tried
 >./configure --prefix=/usr --includedir=/usr/include/boost/python/detail
and then
 > make
and the
 >cvisual.h:8:47: boost/python/detail/wrap_python.hpp: No such file or 
directory
 >cvisual.h:12:34: boost/python/tuple.hpp: No such file or directory
 >cvisual.h:13:33: boost/python/list.hpp: No such file or directory
is always there.
Even if it seems the compiler doesn't find the right path of that file, 
that is
 >/usr/include/boost/python/detail/wrap_python.hpp
I'm not an expert of compiling, so I don't know exactly
what to check to fix the problem. I'll be grateful to anyone's suggestion.
Thanks

-- 

Giuliano 
email			gb...@so...

Re: [Visualpython-users] Debian packages for vpython-3.0.3

[Andy D. <dou...@la...>]

On Wed, 8 Dec 2004, Floris Bruynooghe wrote:

> Hello
>
> I've upgraded my initial Debian packages for vpython-3.0.3  You can
> still get them from http://www.soton.ac.uk/~fb102/Debian including
> i386 binary builds.

Thanks!  I tried this on an UltraSparc 5 running Debian.  It built,
installed, and ran just fine.  I did have to move my old Visual
installation out of the way to make sure python picked up this one, but
that's a general problem, not one specific to this package.

-- 
    Andy Dougherty		dou...@la...

[Visualpython-users] Debian packages for vpython-3.0.3

[Floris B. <fb...@so...>]

Hello

I've upgraded my initial Debian packages for vpython-3.0.3  You can
still get them from http://www.soton.ac.uk/~fb102/Debian including
i386 binary builds.

Same ristrictions apply: only for the default python version currently
in sarge, so no pythonX.Y-visual packages (yet).  Not that that should
be any limitation really.

And I'm still intrested in bugs, hints, tips and other feedback... :)

Floris

-- 
Debian GNU/Linux -- The power of freedom
www.debian.org | www.gnu.org | www.kernel.org

[flub: Re: [Visualpython-users] packaging issues/bugs]

[Floris B. <fb...@so...>]

Oops, discovered I didn't do a list reply here... sorry

----- Forwarded message from flub -----

> To: Jonathan Brandmeyer <jbr...@ea...>
> Subject: Re: [Visualpython-users] packaging issues/bugs
> User-Agent: Mutt/1.5.6+20040722i
> Date: Wed, 8 Dec 2004 12:15:26 +0000
> 
> On Mon, Dec 06, 2004 at 11:04:46PM -0500, Jonathan Brandmeyer wrote:
> > I noticed that you are not an official Debian Developer (according to
> > people.debian.org).  Out of curiosity, is this packaging effort part of
> > an application to become one?
> 
> I am indeed not.  Initially I just wanted a nice package on my own
> system for VPython.  But I might consider applying for DD and maintain
> python-visual officially if I think I can commit the time for it.
> I'll see how it goes.
> 
> Floris
> 
> -- 
> Debian GNU/Linux -- The power of freedom
> www.debian.org | www.gnu.org | www.kernel.org
> 
> rs mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users
> Status: RO
> X-Status: A
> Content-Length: 1764
> Lines: 44
> 
> .1 required=5.0 tests=AWL,BAYES_00,
> 	RCVD_NUMERIC_HELO,TO_ADDRESS_EQ_REAL autolearn=no version=2.64
> Status: O
> Content-Length: 1764
> Lines: 44
> 
> On Mon, 2004-12-06 at 19:49 +0000, Floris Bruynooghe wrote:
> > Not sure if this is the right place for this really, this is a -users
> > list after all...
> > 
> > Anyway:
> > I've been playing around a bit with the package and ran accros the
> > following issues wich would be nice to see fixed.
> 
> I'll look into these issues when I get a chance.  I am in the middle of
> semester exams, and won't be able to set aside some time for this until
> next week.
> 
> 
> > This is fairly clear.  Why is cvisual not using a Makefile.am?  If you
> > could wirite a Makefile.am this would be solved automatically.
> 
> Because Automake and libtool wants to force me into a model of building
> libraries that is flat wrong for i386-pc-mingw32 and
> powerpc-apple-darwin*.  Since it only worked properly for one out of the
> three platforms that VPython is directly supported on, I chose to write
> my own single Makefile.in rather than maintain three (or even just two)
> separate build procedures.
> 
> All of the issues that you mentioned are straightforward to fix, and I
> will be happy to do so.  If you want to submit a patch, I would be
> grateful.
> 
> I noticed that you are not an official Debian Developer (according to
> people.debian.org).  Out of curiosity, is this packaging effort part of
> an application to become one?
> 
> -Jonathan
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now. 
> http://productguide.itmanagersjournal.com/
> ___________________________________________
----- End forwarded message -----

-- 
Debian GNU/Linux -- The power of freedom
www.debian.org | www.gnu.org | www.kernel.org

Re: [Visualpython-users] Idle problems on OSX (Was: VPython and Python 2.4)

[Jonathan B. <jbr...@ea...>]

On Tue, 2004-12-07 at 23:46 -0500, Jon Schull wrote:
> Although I can run vpython programs under python (osx 10.3.6), I cannot 
> run vpython.
> 
> I get this error:

Since this is a problem with Idle, you should be asking the Idle
developers about it.  The "vpython" script is nothing more than a
forwarding shell script that starts up the stock Idle for Python 2.3.

-Jonathan

Re: [Visualpython-users] VPython and Python 2.4

[Jon S. <js...@so...>]

Although I can run vpython programs under python (osx 10.3.6), I cannot 
run vpython.

I get this error:

208-186-56-189:~ jis$ vpython
Traceback (most recent call last):
   File "<string>", line 1, in ?
   File "/sw/lib/python2.3/idlelib/run.py", line 7, in ?
     import threading
   File "/sw/lib/python2.3/threading.py", line 13, in ?
     from traceback import print_exc as _print_exc
ImportError: cannot import name print_exc

[at this point I must type ctrl-c]

^CTraceback (most recent call last):
   File "/sw/lib/python2.3/idlelib/idle", line 21, in ?
     PyShell.main()
   File "/sw/lib/python2.3/idlelib/PyShell.py", line 1287, in main
     flist.pyshell = PyShell(flist)
   File "/sw/lib/python2.3/idlelib/PyShell.py", line 769, in __init__
     self.interp.start_subprocess()
   File "/sw/lib/python2.3/idlelib/PyShell.py", line 362, in 
start_subprocess
     self.rpcclt.accept()
   File "/sw/lib/python2.3/idlelib/rpc.py", line 526, in accept
     working_sock, address = self.listening_sock.accept()
   File "/sw/lib/python2.3/socket.py", line 167, in accept
     sock, addr = self._sock.accept()
KeyboardInterrupt


208-186-56-189:~ jis$ python
Python 2.3.4 (#1, Nov  7 2004, 14:21:14)
[GCC 3.3 20030304 (Apple Computer, Inc. build 1495)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
 >>>

I'd welcome suggestions.   (and will continue to hope that someone will 
roll vpython into a mcEnthon package)

thanks



=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Jon Schull, Ph.D.
Associate Professor
Information Technology
Rochester Institute of Technology
102 Lomb Memorial Drive
Rochester, New York 14623
sc...@di... 585-738-6696

Re: [Visualpython-users] packaging issues/bugs

[Jonathan B. <jbr...@ea...>]

On Mon, 2004-12-06 at 19:49 +0000, Floris Bruynooghe wrote:
> Not sure if this is the right place for this really, this is a -users
> list after all...
> 
> Anyway:
> I've been playing around a bit with the package and ran accros the
> following issues wich would be nice to see fixed.

I'll look into these issues when I get a chance.  I am in the middle of
semester exams, and won't be able to set aside some time for this until
next week.


> This is fairly clear.  Why is cvisual not using a Makefile.am?  If you
> could wirite a Makefile.am this would be solved automatically.

Because Automake and libtool wants to force me into a model of building
libraries that is flat wrong for i386-pc-mingw32 and
powerpc-apple-darwin*.  Since it only worked properly for one out of the
three platforms that VPython is directly supported on, I chose to write
my own single Makefile.in rather than maintain three (or even just two)
separate build procedures.

All of the issues that you mentioned are straightforward to fix, and I
will be happy to do so.  If you want to submit a patch, I would be
grateful.

I noticed that you are not an official Debian Developer (according to
people.debian.org).  Out of curiosity, is this packaging effort part of
an application to become one?

-Jonathan

Re: [Visualpython-users] VPython and Python 2.4

[Jonathan B. <jbr...@ea...>]

On Mon, 2004-12-06 at 12:58 -0800, Kev...@ca... wrote:
> 
> 
> 
> I ran into an error running VPython-MSWindows_3.0.2.exe with Python-2.4.msi
> It wanted python23.dll and couldn't find it.
> The DLL has been renamed in Python 2.4 to python24.dll.
> I went back to Python 2.3.4 so that I could use VPython.
> When I went back to Python 2.3.4, installing Vpython put files in
> C:\Python24, so I had to go into the registry and remove obsolete entries.
> 
> Any suggestions on how to move to Python 2.4?
> Did I install incorrectly?  I went from 2.3.4+3.0.2 to 2.4+3.0.2 and back
> to 2.3.4+3.0.2.
> I'd really like to stay current.
> I could try going into the VPython binaries and change references of
> python23 to python24, but I hate to do this.
> 
> Regards,
>           Kevin   x57048

VPython will have to be rebuilt from source for Python 2.4.  I would be
able to provide a build sometime in the middle of next week, since I am
in the middle of semester exams right now.

-Jonathan

[Visualpython-users] VPython and Python 2.4

[<Kev...@ca...>]

I ran into an error running VPython-MSWindows_3.0.2.exe with Python-2.4.msi
It wanted python23.dll and couldn't find it.
The DLL has been renamed in Python 2.4 to python24.dll.
I went back to Python 2.3.4 so that I could use VPython.
When I went back to Python 2.3.4, installing Vpython put files in
C:\Python24, so I had to go into the registry and remove obsolete entries.

Any suggestions on how to move to Python 2.4?
Did I install incorrectly?  I went from 2.3.4+3.0.2 to 2.4+3.0.2 and back
to 2.3.4+3.0.2.
I'd really like to stay current.
I could try going into the VPython binaries and change references of
python23 to python24, but I hate to do this.

Regards,
          Kevin   x57048

[Visualpython-users] packaging issues/bugs

[Floris B. <fb...@so...>]

Not sure if this is the right place for this really, this is a -users
list after all...

Anyway:
I've been playing around a bit with the package and ran accros the
following issues wich would be nice to see fixed.

[These notes are from visual-3.0.2 but seem still to be valid with
3.0.3]

* When unistalling the package this fails:
flub@laurie:/usr/local/src/visual-3.0.2$ ssu make uninstall
Making uninstall in visual
make[1]: Entering directory `/usr/local/src/visual-3.0.2/visual'
list='__init__.py controls.py crayola.py factorial.py graph.py
macevent.py primitives.py text.py ui.py'; for p in $list; do \
  d=`echo "$p" | sed -e 's,^.*/,,'`; \
  rm -f /usr/local/lib/python2.3/site-packages/visual/$d; \
  rm -f /usr/local/lib/python2.3/site-packages/visual/${d}c; \
  rm -f /usr/local/lib/python2.3/site-packages/visual/${d}o; \
done
make[1]: Leaving directory `/usr/local/src/visual-3.0.2/visual'
Making uninstall in cvisual
make[1]: Entering directory `/usr/local/src/visual-3.0.2/cvisual'
make[1]: *** No rule to make target `uninstall'.  Stop.
make[1]: Leaving directory `/usr/local/src/visual-3.0.2/cvisual'
make: *** [uninstall-recursive] Error 1

This is fairly clear.  Why is cvisual not using a Makefile.am?  If you
could wirite a Makefile.am this would be solved automatically.


* Continuing on this, when doing make unistall inside visual this still
leaves the empty directories behind: .../site-packages/visual,
..../visual/demos, ..../visual/docs, ..../visual/idle_VPython


* The documentation is installed in a rather odd place, wouldn't it be
  better to install in to $(prefix)/share/doc/$(package_name), the
  demos could then be installed into
  $(prefix)/share/doc/$(package_name)/[demos|examples]/ which would
  also make more sense.  I know automake doesn't support html
  documentation but you should still have enough control to do it
  yourself.


* When configuring the package with "./configure --disable-docs
  --disable-demos --disable-idle-vpython" the directories
  (.../visual/docs, .../visual/demos, .../visual/idel_VPyton) are still
  installed, but left empty.  Also the $(prefix)/bin/vpython script is
  still installed when using --disable-idle-vpython.  This shouldn't be
  imho.

  I recon the directories should not be there at all in these cases.
  Or is there some reasoning behind this?


* This might be marginal and an actual automake issue and indeed is
  not very important.  But the installation also fails when
  $(prefix)/bin does not exist.  Maybe in other places installation
  also fails if the parent directory is not there, I haven't had this
  situation.  But I recon the parent directories should be made when
  not there.  (cp --parents or install --directory or so)


I've discovered these problems while trying to make a debian package.
Currently it only is visual 3.0.2 and only works with debians default
python version in sarge (and sid?).  If you want to have a look or
test it (I would not mind some testing really ;-)) you can grab the
files at http://www.soton.ac.uk/~fb102/Debian/ including a i386 build.
I should be able to generate a sparc build as well but can't test that
really as I only have remote access to that machine for now.  If anyone
is intrested, let me know.

In regard to packaging it would be nice if there was a changelog kept.
It would be obvious what to look out for in that case...  The changes
are summarised in the relaese email so just write that down in a
changelog file.  Anyway, this is purely convenience.  If you recon
this is to much hassle for what benefits it returns just forget about
it.


Cheers
Floris


-- 
Debian GNU/Linux -- The power of freedom
www.debian.org | www.gnu.org | www.kernel.org

[Visualpython-users] error in text.py

[<Kev...@ca...>]

Sorry if my terms are incorrect.  I'm new to Python and VPython.
I'm using vpython 3.0.3  & 3.0.2

Creating TEXT without specifying a color generates an error.
The __init__ method does not handle color equal to None.  Reshape does.

example:
from visual import *
from visual.text import *
t=text(string='ABC')
t=text(string='ABC',color=color.red)

>>> from visual import *
Visual 2004-12-03
>>> from visual.text import *
>>> t=text(string='ABC')
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "C:\Python23\lib\site-packages\visual\text.py", line 331, in
__init__
    depth, color, container, visible)
  File "C:\Python23\lib\site-packages\visual\text.py", line 363, in
showletter
    thickness, color, container, visible)
  File "C:\Python23\lib\site-packages\visual\text.py", line 342, in
makeletterbox
    b = convex(display=self.display, color=color, frame=container,
visible=visible)
  File "C:\Python23\lib\site-packages\visual\primitives.py", line 288, in
__init__
    process_init_args_from_keyword_dictionary(self, keywords)
  File "C:\Python23\lib\site-packages\visual\primitives.py", line 37, in
process_init_args_from_keyword_dictionary
    displayobject.color =  keywords['color']
Boost.Python.ArgumentError: Python argument types in
    None.None(convex, NoneType)
did not match C++ signature:
    None(visual::convex {lvalue}, visual::rgb)
>>> t=text(string='ABC',color=color.red)
>>>

It works fine when text.py is modified to check if color defaulted:
class text:
    def __init__(self, pos=(0,0,0), axis=defaultdir, string='',
justify='left',
           height=1.0, width=None, depth=0, color=None, up=None, visible=1,
           display=None):
        if display == None:
            display = scene
        self.display = display
>>      if color == None:
>>          color = display.foreground

Regards,
          Kevin   x57048

[Visualpython-users] Release: 3.0.3

[Jonathan B. <jbr...@ea...>]

This release makes a handful of small changes:
vector.__pos__ has been enabled; it returns a copy of self.
vector.__abs__ has been enabled; it returns self.mag.
All module-private functions have been prefixed with a single leading 
	underscore to denote that they are private/protected.
Some demo programs have been updated.
The INSTALL.txt instructions have been updated.

The release is available from the Sourceforge download page:
http://sourceforge.net/project/showfiles.php?group_id=6013&package_id=6822

-Jonathan Brandmeyer

Re: [Visualpython-users] building visual-3.0 on Debian sarge (testing)

[Jonathan B. <jbr...@ea...>]

On Sat, 2004-12-04 at 12:44 +0000, Sanjoy Mahajan wrote:
> I'm using 'visual-3.0-20040722.tar.gz'.
> 
> The config.log and the resulting top-level Makefile claim the visual
> version is 2.9.7, I think because the 'configure' script has these
> lines:
> 
>   PACKAGE_VERSION='2.9.7'
>   PACKAGE_STRING='Visual Python 2.9.7'
> 
> Should the version become 3.0.0?

> A few updates for the 'INSTALL.txt':
> 
These things have been fixed in later releases, as well as a few other
bugs.  3.0.3 was released to the Sourceforge page yesterday.

> I couldn't compile visual on my 96MB Pentium (586) laptop -- the g++
> compile of 'cvisualmodule.cpp' consumed over 150MB of virtual memory
> (c++ is an absurd language)!  The cc1plus process got about 2% of the
> CPU time while swapping like mad.  I then compiled everything on a
> nearby workstation with more memory, but is there any way to reduce
> the memory consumption?
> 
> -Sanjoy

There is, but only at the cost of even longer total compile times.  I
have targeted 256MB of ram as the minimum for building Visual; the
runtime requirement is much lower.

If a packaging expert provided us with an up to date debian/ directory I
would be more than happy to provide a prebuilt .deb for download.

-Jonathan

[Visualpython-users] building visual-3.0 on Debian sarge (testing)

[Sanjoy M. <sa...@mr...>]

I'm using 'visual-3.0-20040722.tar.gz'.

The config.log and the resulting top-level Makefile claim the visual
version is 2.9.7, I think because the 'configure' script has these
lines:

  PACKAGE_VERSION='2.9.7'
  PACKAGE_STRING='Visual Python 2.9.7'

Should the version become 3.0.0?

A few updates for the 'INSTALL.txt':

I'm using Debian testing (sarge).  To build visual-3.0 I had to
install xlibmesa-gl-dev and xlibmesa-glu-dev to get 'GL/gl.h' and
'GL/glu.h' (needed when compiling 'cylinder.cpp').  These are the
error lines I saw before I installed those packages:

  xgl.h:22:19: GL/gl.h: No such file or directory
  xgl.h:23:20: GL/glu.h: No such file or directory

Sarge now (4 Dec 2004) has v1.31 of libboost-python-dev so no need to
use python2.2 packages or to forage in Sid.

So the one-shot apt-get line I recommend is:

  apt-get install python2.3-{dev,numeric} g++-3.3 {libboost-python,xlibmesa-gl{,u},gtkglarea5,libgtk1.2}-dev

or with \ to break the long line:

  apt-get install python2.3-{dev,numeric} g++-3.3 \
          {libboost-python,xlibmesa-gl{,u},gtkglarea5,libgtk1.2}-dev

Either is equivalent to:

  apt-get install python2.3-dev python2.3-numeric g++-3.3 \
	  libboost-python-dev xlibmesa-gl-dev xlibmesa-glu-dev \
	  gtkglarea5-dev libgtk1.2-dev

I couldn't compile visual on my 96MB Pentium (586) laptop -- the g++
compile of 'cvisualmodule.cpp' consumed over 150MB of virtual memory
(c++ is an absurd language)!  The cc1plus process got about 2% of the
CPU time while swapping like mad.  I then compiled everything on a
nearby workstation with more memory, but is there any way to reduce
the memory consumption?

-Sanjoy

[Visualpython-users] vpythyon simulations/demonstrations semiconductors

[axawire <ax...@ch...>]

Hi,

 

About a year ago I was in a physics class that used Matter and Interactions,
Vol 2 with VPython.  The semiconductor section chapter 25 was not covered.
I was wondering if there are any semiconductor simulations out there in
v-python already that demonstrate the processes that occur with
semiconductors.

 

Thanks,

 

Rich


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.801 / Virus Database: 544 - Release Date: 11/24/2004
 

Re: [Visualpython-users] Debian Sarge (Sid?) package dependencies

[Jonathan B. <jbr...@ea...>]

On Wed, 2004-12-01 at 00:17 +0000, Floris Bruynooghe wrote:
> Hi
> 
> Installing Vpython 3.0.2 (got the source form sourceforge) the
> INSTALL.txt file suggests some packages for Debian.  Some errors (or
> just outdated) information though.
> 
> Firstly the problem of libboost-python-dev is resolved in sarge as
> version 1.31.0 got in.
> 
> Secondly the package xlibmesa-glu-dev (which depends on
> xlibmesa-gl-dev) is required as well as gtkglarea5-dev.  Maybe
> gtkglarea5-dev did depend on them before, but not now.

Thanks for the heads-up.  This is what I have committed to CVS:

   Users of Debian Sid, Sarge, and derivatives will need these packages:
	python2.3-dev
	python2.3-numeric
	gtkglarea5-dev
	libgtk1.2-dev
	g++
	libboost-python-dev
	libglu-dev (xlibmesa-glu-dev OR nvidia-glx-dev) **

** libglu-dev doesn't exist; it is Provided by other packages.  If you
use Mesa+DRI, then xlibmesa-glu-dev will meet this requirement.  If you
use NVIDIA's non-free OpenGL drivers you will need nvidia-glx-dev.
Other drivers may require you to use a specific -dev package for that
driver.

(end)

Oddly enough, even though nvidia-glx-dev Depends on xlibmesa-glu-dev and
xlibmesa-gl-dev, it is not enough to have those two packages alone on
your system if you have the nvidia-glx packages installed.  Go figure.
If you have anything else you want me to add, please let me know.

-Jonathan

[Visualpython-users] Debian Sarge (Sid?) package dependencies

[Floris B. <fb...@so...>]

Hi

Installing Vpython 3.0.2 (got the source form sourceforge) the
INSTALL.txt file suggests some packages for Debian.  Some errors (or
just outdated) information though.

Firstly the problem of libboost-python-dev is resolved in sarge as
version 1.31.0 got in.

Secondly the package xlibmesa-glu-dev (which depends on
xlibmesa-gl-dev) is required as well as gtkglarea5-dev.  Maybe
gtkglarea5-dev did depend on them before, but not now.

Hope this helps
Floris

-- 
Debian GNU/Linux -- The power of freedom
www.debian.org | www.gnu.org | www.kernel.org

Re: [Visualpython-users] MacEnthon

[Jon S. <js...@so...>]

> Side note: The main reason that we do not provide a framework build of
> Visual against the Apple-supplied Python 2.3, is that the 
> Apple-supplied
> Python does not provide Idle or TkInter.  The second reason is that it
> would be a major pain to also build and ship a complete set of gtk+
> libs, independent of the Fink project.

However, a framework of this sort (including gtk+ libs, would  be most 
welcome, since it is a major pain for most mac users to work in 
fink/x11.  TkInter is available.  Moreover there is now a working QT on 
the mac along with an  Eric3 editor that looks quite excellent.    
http://www.die-offenbachs.de/detlev/eric3.html

It would be very nice to have a font-smoothing, first class mac IDE for 
python and vpython work on the mac and to not have to worry about 
multiple pythons.

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Jon Schull, Ph.D.
Associate Professor
Information Technology
Rochester Institute of Technology
102 Lomb Memorial Drive
Rochester, New York 14623
sc...@di... 585-738-6696