Re: Python Portability

2010-08-09 Thread rantingrick
On Aug 8, 8:03 am, "W. eWatson" wrote: > I'm done here. Well thats just great, now how will we ever know what the one char change was. Hmm. >>> a = 'somestring' >>> -a Traceback (most recent call last): File "", line 1, in -a TypeError: bad operand type for unary -: 'str' Go figure! -

Re: Python Portability

2010-08-09 Thread geremy condra
On Sun, Aug 8, 2010 at 11:57 PM, Lawrence D'Oliveiro wrote: > In message , W. eWatson wrote: > >> Believe me I had no intent of expanding this thread beyond looking for a >> straight and simple insight to Python distribution (portability, >> whatever) and how to get my partner squared away. The ge

Re: Python Portability

2010-08-09 Thread Lawrence D'Oliveiro
In message , W. eWatson wrote: > Believe me I had no intent of expanding this thread beyond looking for a > straight and simple insight to Python distribution (portability, > whatever) and how to get my partner squared away. The general issue > seems to drifted off on its own accord. “Drifted off

Re: Python Portability

2010-08-08 Thread alex23
"W. eWatson" wrote: > I now have the answer I need, and I do not care one more wit > about a one character change. > > I'm done here. That's a fantastic response to give to people who were actually willing to sacrifice their time to help you with your problems. I'm always stunned at those who com

Re: Python Portability

2010-08-08 Thread Martin v. Loewis
> Add-Remove would be a very good answer, except for one thing. Understand > that I'm in Win7 so CP takes on a different form. On Control Panel > Add-Remove, I can find exactly two Python files: Python 2.5, and > python-Numpy-1.2.0. No scipy anything. Well, it should be there. Perhaps it was inst

Re: Python Portability

2010-08-08 Thread W. eWatson
On 8/8/2010 4:08 AM, David Cournapeau wrote: ... python-Numpy-1.2.0. No scipy anything. Well, this is interesting. I just noticed Martin v. Loewis on the Python 2.5 entry. That's you, right? You are conflating so many issues at the same time, it is very difficult to follow what you are doing.

Re: Python Portability

2010-08-08 Thread David Cournapeau
On Sun, Aug 8, 2010 at 10:10 AM, W. eWatson wrote: > On 8/7/2010 4:45 PM, Martin v. Loewis wrote: >>> >>> To add to the msg I just sent to M. Torrie. We are given the msi >>> programs for Python, PIL,matplotlib, and numpy. The question of how to >>> uninstall and re-install a different version rem

Re: Python Portability

2010-08-08 Thread Thomas Jollans
On 08/08/2010 03:10 AM, W. eWatson wrote: > I think I posted the errors my partner got above. Let me look. Yes, > here's the copy. > He gets > > Traceback (most recent call last): > File "C:\Documents and > Settings\HP_Administrator.DavesDesktop\Desktop\NC-FireballReport20100729.py", > line 40,

Re: Python Portability

2010-08-07 Thread W. eWatson
On 8/7/2010 4:45 PM, Martin v. Loewis wrote: To add to the msg I just sent to M. Torrie. We are given the msi programs for Python, PIL,matplotlib, and numpy. The question of how to uninstall and re-install a different version remains. I'd claim that this is not the real question. The real quest

Re: Python Portability

2010-08-07 Thread Martin v. Loewis
> To add to the msg I just sent to M. Torrie. We are given the msi > programs for Python, PIL,matplotlib, and numpy. The question of how to > uninstall and re-install a different version remains. I'd claim that this is not the real question. The real question is, instead: "What specific error did

Re: Python Portability--Not very portable?

2010-08-07 Thread Ben Finney
"W. eWatson" writes: > Yes, code reversal programs have been around for many, many decades. > Try one on MS Word or Adobe Acrobat. :-) Interesting examples. What “important stuff” from those programs has not been “ripped off”, to use your terms? Is there anything remaining in those programs whi

Re: Python Portability

2010-08-07 Thread W. eWatson
On 8/7/2010 2:26 PM, Martin v. Loewis wrote: Am 07.08.2010 23:01, schrieb Michael Torrie: On 08/07/2010 01:17 PM, W. eWatson wrote: Presumably I have him somehow delete the numpy site-package, the numpy 1.2.0 package? Just drill his way dow from the .../lib/site_packages? Then install 1.2.0. He

Re: Python Portability

2010-08-07 Thread W. eWatson
On 8/7/2010 2:01 PM, Michael Torrie wrote: On 08/07/2010 01:17 PM, W. eWatson wrote: Presumably I have him somehow delete the numpy site-package, the numpy 1.2.0 package? Just drill his way dow from the .../lib/site_packages? Then install 1.2.0. He's missed the boat on that before by not followi

Re: Python Portability

2010-08-07 Thread Martin v. Loewis
Am 07.08.2010 23:01, schrieb Michael Torrie: > On 08/07/2010 01:17 PM, W. eWatson wrote: >> Presumably I have him somehow delete the numpy site-package, the numpy >> 1.2.0 package? Just drill his way dow from the .../lib/site_packages? >> Then install 1.2.0. He's missed the boat on that before by

Re: Python Portability

2010-08-07 Thread Michael Torrie
On 08/07/2010 01:17 PM, W. eWatson wrote: > Presumably I have him somehow delete the numpy site-package, the numpy > 1.2.0 package? Just drill his way dow from the .../lib/site_packages? > Then install 1.2.0. He's missed the boat on that before by not following > instructions. Wait. I'm confus

Re: Python Portability--Not very portable?

2010-08-07 Thread Martin v. Loewis
> As an example, my inexperienced Python partner 30 miles away has gotten > out of step somehow. I think by installing a different version of numpy > than I use. I gave him a program we both use months ago, and he had no > trouble. (We both use IDLE on 2.5). I made a one character change to it > an

Re: Python Portability

2010-08-07 Thread W. eWatson
On 8/6/2010 2:23 AM, Lawrence D'Oliveiro wrote: In message, W. eWatson wrote: I made a one character change to it and sent him the new py file. He can't execute it. What exactly was the problem? I put a minus sign in front of a variable. I had him use the shell to check his version numpy, w

Re: Python Portability--Not very portable?

2010-08-06 Thread Steven D'Aprano
On Fri, 06 Aug 2010 10:58:24 -0700, W. eWatson wrote: > Is there a complete illustration of using disutils? Our only > dependencies are on Python Org material. We use no commercial or > licensed code. Oh my, the sheer ignorance that sentence reveals. Python and the standard library *is* licensed

Re: Python Portability--Not very portable?

2010-08-06 Thread Steven D'Aprano
On Thu, 05 Aug 2010 18:50:14 -0700, W. eWatson wrote: > As an example, my inexperienced Python partner 30 miles away has gotten > out of step somehow. I think by installing a different version of numpy > than I use. I gave him a program we both use months ago, and he had no > trouble. (We both use

Re: Python Portability--Not very portable?

2010-08-06 Thread Steven D'Aprano
On Fri, 06 Aug 2010 10:35:38 -0700, W. eWatson wrote: > So you think Python is part of open software in terms of distributing a > "product"? Python itself *is* open source software. It doesn't *require* you to write open source software. > So I should stick to C, where one can distribute progra

Re: Python Portability--Not very portable?

2010-08-06 Thread Steven D'Aprano
On Fri, 06 Aug 2010 08:00:55 -0700, W. eWatson wrote: >>> I would think there are some small time and big time Python players >>> who sell executable versions of their programs for profit? >> >> Yes. What's your point? > That someone must know how to distribute them without having the source > cod

Re: Python Portability--Not very portable?

2010-08-06 Thread geremy condra
On Fri, Aug 6, 2010 at 10:58 AM, W. eWatson wrote: > Is there a complete illustration of using disutils? Our only dependencies > are on Python Org material. We use no commercial or licensed code. http://tinyurl.com/3yhwjfj Geremy Condra -- http://mail.python.org/mailman/listinfo/python-list

Re: Python Portability--Not very portable?

2010-08-06 Thread CM
> As an example, my inexperienced Python partner 30 miles away has gotten > out of step somehow. I think by installing a different version of numpy > than I use. I gave him a program we both use months ago, and he had no > trouble. (We both use IDLE on 2.5). I made a one character change to it > an

Re: Python Portability--Not very portable?

2010-08-06 Thread CM
On Aug 5, 9:50 pm, "W. eWatson" wrote: > In my on-again-off-again experience with Python for 18 months, > portability seems an issue. > > As an example, my inexperienced Python partner 30 miles away has gotten > out of step somehow. I think by installing a different version of numpy > than I use.

Re: Python Portability--Not very portable?

2010-08-06 Thread Peter Otten
W. eWatson wrote: > So you think Python is part of open software in terms of distributing a > "product"? So I should stick to C, where one can distribute programs w/o > revealing code details, and having a customer compile the code? It's No, I'm trying to make you reconsider what you're going to

Re: Python Portability--Not very portable?

2010-08-06 Thread W. eWatson
On 8/6/2010 10:31 AM, geremy condra wrote: On Fri, Aug 6, 2010 at 8:00 AM, W. eWatson wrote: I would think there are some small time and big time Python players who sell executable versions of their programs for profit? Yes. What's your point? That someone must know how to distribute them

Re: Python Portability--Not very portable?

2010-08-06 Thread W. eWatson
On 8/6/2010 9:03 AM, Peter Otten wrote: ... Seriously, I try to make a joke once in a while, usually with devastating results. The idea you were meant to take away was that once you start thinking about a protection scheme there is always a next step until you reach the point where your software

Re: Python Portability--Not very portable?

2010-08-06 Thread geremy condra
On Fri, Aug 6, 2010 at 8:00 AM, W. eWatson wrote: > >>> I would think there are some small time and big time Python players who >>> sell >>> executable versions of their programs for profit? >> >> Yes. What's your point? > > That someone must know how to distribute them without having the source c

Re: Python Portability--Not very portable?

2010-08-06 Thread Peter Otten
W. eWatson wrote: > I can't respond to otten directly, since he uses gmane. Here's my > response. > > W. eWatson wrote: > > >>> >>> I would think there are some small time and big time Python > players who > >>> >>> sell executable versions of their programs for profit? > >> >> > >> >> Yes.

Re: Python Portability--Not very portable?

2010-08-06 Thread W. eWatson
I can't respond to otten directly, since he uses gmane. Here's my response. W. eWatson wrote: >>> >>> I would think there are some small time and big time Python players who >>> >>> sell executable versions of their programs for profit? >> >> >> >> Yes. What's your point? > > That someone must

Re: Python Portability--Not very portable?

2010-08-06 Thread Peter Otten
W. eWatson wrote: >>> I would think there are some small time and big time Python players who >>> sell executable versions of their programs for profit? >> >> Yes. What's your point? > That someone must know how to distribute them without having the source > code ripped off. Yes, but he won't tel

Re: Python Portability--Not very portable?

2010-08-06 Thread W. eWatson
I would think there are some small time and big time Python players who sell executable versions of their programs for profit? Yes. What's your point? That someone must know how to distribute them without having the source code ripped off. disutils. Sounds familiar. I'm pretty sure I was u

Re: Python Portability--Not very portable?

2010-08-06 Thread Tiago Katcipis
On Fri, Aug 6, 2010 at 12:28 AM, W. eWatson wrote: > On 8/5/2010 7:45 PM, geremy condra wrote: > >> On Thu, Aug 5, 2010 at 6:50 PM, W. eWatson >> wrote: >> >>> In my on-again-off-again experience with Python for 18 months, >>> portability >>> >>> seems an issue. >>> >>> As an example, my inexper

Re: Python Portability

2010-08-06 Thread Lawrence D'Oliveiro
In message , W. eWatson wrote: > I made a one character change to it and sent him the new py file. He can't > execute it. What exactly was the problem? -- http://mail.python.org/mailman/listinfo/python-list

Re: Python Portability--Not very portable?

2010-08-05 Thread geremy condra
On Thu, Aug 5, 2010 at 8:28 PM, W. eWatson wrote: > On 8/5/2010 7:45 PM, geremy condra wrote: >> >> On Thu, Aug 5, 2010 at 6:50 PM, W. eWatson  wrote: >>> >>> In my on-again-off-again experience with Python for 18 months, >>> portability >>> seems an issue. >>> >>> As an example, my inexperienced

Re: Python Portability--Not very portable?

2010-08-05 Thread W. eWatson
On 8/5/2010 7:45 PM, geremy condra wrote: On Thu, Aug 5, 2010 at 6:50 PM, W. eWatson wrote: In my on-again-off-again experience with Python for 18 months, portability seems an issue. As an example, my inexperienced Python partner 30 miles away has gotten out of step somehow. I think by install

Re: Python Portability--Not very portable?

2010-08-05 Thread geremy condra
On Thu, Aug 5, 2010 at 6:50 PM, W. eWatson wrote: > In my on-again-off-again experience with Python for 18 months, portability > seems an issue. > > As an example, my inexperienced Python partner 30 miles away has gotten out > of step somehow. I think by installing a different version of numpy tha

Python Portability--Not very portable?

2010-08-05 Thread W. eWatson
In my on-again-off-again experience with Python for 18 months, portability seems an issue. As an example, my inexperienced Python partner 30 miles away has gotten out of step somehow. I think by installing a different version of numpy than I use. I gave him a program we both use months ago, an