[Pythonmac-SIG] porting VPython to OS X
Hello. I'm an astronomy/physics instructor who makes heavy use of VPython (http://www.vpython.org) in teaching introductory calculus-based physics. Currently, the only way to use VPython under OS X is via Fink, which indeed works very well. However, we *REALLY• need a native OS X port that can run without the need for X11. Neither I nor the original VPython developers are Mac programmers and therein lies the purpose of my request. Is there a kind soul out there who would be willing to port VPython so that it runs with the latest Mac native version of Python (currently 2.5 afaik)? I would be most willing to help with testing and anything else not related to writing Mac code, which I currently just can't do. You would be helping the physics teaching community as well as the Mac and Python communities and there would certainly be undying gratitude from all of us! If you're willing to help us out, contact me on list or off list (email in sig). I would really appreciate it! Joe Heafner heafnerj(at)sticksandshadows(dot)com www(dot)SticksAndShadows(dot)com ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] bugs in _Qtmodule
On Oct 4, 2006, at 5:12 AM, Jack Jansen wrote: > > A patch won't help much, because _Qtmodule is generated (through > qtscan.py/qtsupport.py). I assume that there's a one-line mistake > in qtsupport, which leads to one C type being handled as CmpObj in > stead of CmpInstObj. Ah, I see. Yes a bunch of lines in qtsupport.py > Hmm, well at least the patch will contain that information, I > guess. Could you put it on sourceforge and assign it to me? I'll sourceforge the patch to qtsupport.py; it's obvious. -Jas ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] bugs in _Qtmodule
On 4-okt-2006, at 3:58, Jeff Senn wrote: While attempting to use the QuickTime sequence grabber interfaces from Python I notice that there is some confusion between Component and ComponentInstance in _Qtmodule.c. I believe most of the instances of "CmpObj_{Convert,New}" in _Qtmodule should actually be "CmpInstObj_{Convert,New}" (There are a few that are correctly CmpObj_...) I have a (moderately tested) patch... A patch won't help much, because _Qtmodule is generated (through qtscan.py/qtsupport.py). I assume that there's a one-line mistake in qtsupport, which leads to one C type being handled as CmpObj in stead of CmpInstObj. Hmm, well at least the patch will contain that information, I guess. Could you put it on sourceforge and assign it to me? -- Jack Jansen, <[EMAIL PROTECTED]>, http://www.cwi.nl/~jack If I can't dance I don't want to be part of your revolution -- Emma Goldman smime.p7s Description: S/MIME cryptographic signature ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
[Pythonmac-SIG] bugs in _Qtmodule
While attempting to use the QuickTime sequence grabber interfaces from Python I notice that there is some confusion between Component and ComponentInstance in _Qtmodule.c. I believe most of the instances of "CmpObj_{Convert,New}" in _Qtmodule should actually be "CmpInstObj_{Convert,New}" (There are a few that are correctly CmpObj_...) I have a (moderately tested) patch... -Jas [Please CC relevant replies to me directly as I don't read the list regularly] ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
[Pythonmac-SIG] IDLE (and others), 2.4.3 and Tkinter solution (for me)
I work on 10.3.9 and since i upgrade to python 2.4.3 universal, i cannot run IDLE without freezing but also other apps like mayavi that I must use in my work. Ronald Oussoren writes "but IDLE in MacPython 2.4 doesn't work for me after all. I'm seeing the same behaviour as you: IDLE starts, but hangs immediately " For people like me who cannot update to Tiger (work, money) I found a solution : noting that this problem did not exist with macpython 2.4.1, I replace the Tkinter.so of 2.4.3 by the one of 2.4.1 and no more problem : all works perfectly Martin Martin Laloux Dr Sc. Geologue Université Catholique de Louvain Détaché au M.R.W. - DGRNE Cellule géologie Division de la Prévention et des Autorisations 15, avenue Prince de Liège B-5100 Namur tél. : 081 / 33 61 24 fax : 081 / 33 61 22 mailto:[EMAIL PROTECTED] http://environnement.wallonie.be/cartosig/cartegeologique Ce message n'engage aucunement la DGRNE et reste informel. Tout courrier officiel doit toujours actuellement être confirmé par lettre et revêtu de la signature d'un agent dûment mandaté. ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] Why Do I Explicitly Need MacPython
On Wednesday, October 04, 2006, at 09:28AM, <[EMAIL PROTECTED]> wrote: >On 03.10.2006, at 12:43, Ronald Oussoren wrote: > >> I'm rather happy with setuptools, there are some cosmetic problems >> (like the header-file thingy), but the core seems pretty well >> thought out. The main > >I wouldn't call that a cosmetic problem. It probably affects few >packages, but for those it is a showstopper. You're right, but it is a rather shallow problem. I had implemented a fix for that within the hour, without having looked at the setuptools source before. There are probably more little wringles like those and some of those will be showstoppers for some people. Ronald ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] Why Do I Explicitly Need MacPython
On 03.10.2006, at 19:09, Bob Ippolito wrote: >> Therefore, if it is possible to download and install eggs manually, >> then I am sure there would be a client base for a GUI-based installer >> associated with .egg files. > > It's still very atypical. You'd be coding a GUI client that three > people use. I don't know. It is very hard to say what is "typical" without some hard data. In my immediate work environment I already see very different habits in installingh software, ranging from the PhD student who administrates his own PC as he likes to a large paranoid research lab where only one person is allowed to install software downloaded from the Internet. > There are options with easy_install to do all of these things. I'm > pretty sure there's an option to download packages without installing > them that people use to download the eggs (e.g. for transfer to > another machine or archival), and there's an option to use a > filesystem path instead of the internet for installing packages. That sounds fine. Still, there is always a need for GUI installers in my opinion. > Any other problems you have you should report to distutils-sig so that > they get fixed. It's definitely not going to get any less popular, so > you're going to have to live with setuptools. As long as there are no plans to abandon the standard distutils installation, I feel safe... and I can't find any other problems with setuptools before the one that blocks my packages (all of them) is solved. Konrad. ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] Why Do I Explicitly Need MacPython
On 03.10.2006, at 12:43, Ronald Oussoren wrote: > I have a patch for setuptools 0.7 that includes header files in > eggs and ensures that other setuptools-aware packages see those > during build_ext. PJE has indicated that something like this will > be added to setuptools in 0.7 timeframe. That's good news. I will look at setuptools again when 0.7 is out. > I'm rather happy with setuptools, there are some cosmetic problems > (like the header-file thingy), but the core seems pretty well > thought out. The main I wouldn't call that a cosmetic problem. It probably affects few packages, but for those it is a showstopper. Konrad. ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig