Re: About some problem

2014-01-03 Thread Ethan Furman
On 01/03/2014 12:55 PM, Steven D'Aprano wrote: André Malo wrote: * Steven D'Aprano wrote: Mark Lawrence wrote: raise "Not Valid DB Type" is perfectly valid in Python 2. Actually, no it isn't. It's only valid up to Python 2.4. In Python 2.5, string exceptions display a warning but continu

Re: About some problem

2014-01-03 Thread Steven D'Aprano
André Malo wrote: > * Steven D'Aprano wrote: > >> Mark Lawrence wrote: >> >>> raise "Not Valid DB Type" >>> >>> is perfectly valid in Python 2. >> >> Actually, no it isn't. It's only valid up to Python 2.4. In Python 2.5, >> string exceptions display a warning but continue to work, and in Pyth

Re: About some problem

2014-01-03 Thread André Malo
* Steven D'Aprano wrote: > Mark Lawrence wrote: > >> raise "Not Valid DB Type" >> >> is perfectly valid in Python 2. > > Actually, no it isn't. It's only valid up to Python 2.4. In Python 2.5, > string exceptions display a warning but continue to work, and in Python > 2.6 they generate a compil

Re: About some problem

2014-01-02 Thread Mark Lawrence
On 03/01/2014 04:18, Ethan Furman wrote: On 01/02/2014 05:14 PM, Mark Lawrence wrote: On 02/01/2014 23:49, Steven D'Aprano wrote: Mark Lawrence wrote: raise "Not Valid DB Type" is perfectly valid in Python 2. Actually, no it isn't. It's only valid up to Python 2.4. In Python 2.5, string ex

Re: About some problem

2014-01-02 Thread Ethan Furman
On 01/02/2014 05:14 PM, Mark Lawrence wrote: On 02/01/2014 23:49, Steven D'Aprano wrote: Mark Lawrence wrote: raise "Not Valid DB Type" is perfectly valid in Python 2. Actually, no it isn't. It's only valid up to Python 2.4. In Python 2.5, string exceptions display a warning but continue to

Re: About some problem

2014-01-02 Thread Larry Hudson
On 01/02/2014 08:31 AM, raj kumar wrote: Hello, I am beginner to python and i am writing following code from pytesser import * and i am getting an error as follow Traceback (most recent call last): File "", line 1, in File "C:\Python33\lib\site-packages\pytesser.py", line 61 print

Re: About some problem

2014-01-02 Thread Mark Lawrence
On 02/01/2014 23:49, Steven D'Aprano wrote: Mark Lawrence wrote: raise "Not Valid DB Type" is perfectly valid in Python 2. Actually, no it isn't. It's only valid up to Python 2.4. In Python 2.5, string exceptions display a warning but continue to work, and in Python 2.6 they generate a compi

Re: About some problem

2014-01-02 Thread Steven D'Aprano
Mark Lawrence wrote: > raise "Not Valid DB Type" > > is perfectly valid in Python 2. Actually, no it isn't. It's only valid up to Python 2.4. In Python 2.5, string exceptions display a warning but continue to work, and in Python 2.6 they generate a compile-time SyntaxError. You know how the wo

Re: About some problem

2014-01-02 Thread Mark Lawrence
On 02/01/2014 17:46, Rustom Mody wrote: Oh ok I get what you are saying: python3 will not recognize a python2 package and install it seemingly correctly but actually wrongly No, it will install it quite correctly. What it won't know is that some of the code is valid in Python 2 but invalid

Re: About some problem

2014-01-02 Thread David Hutto
Looks like you have a a list of 2.7 dependencies in the path args. The first you seem to have 3.3 args, and the second a longer list of 2.7 argsI would assume the second is the full list...correct? On Thu, Jan 2, 2014 at 1:07 PM, David Hutto wrote: > I think, but haven't tried, and this

Re: About some problem

2014-01-02 Thread David Hutto
and as I usually do, keep with the older stable version in order to keep up with other packages compatibiity. On Thu, Jan 2, 2014 at 1:07 PM, David Hutto wrote: > I think, but haven't tried, and this would be 2-3 from __future__ import > > > On Thu, Jan 2, 2014 at 12:46 PM, Rustom Mody wrote:

Re: About some problem

2014-01-02 Thread David Hutto
I think, but haven't tried, and this would be 2-3 from __future__ import On Thu, Jan 2, 2014 at 12:46 PM, Rustom Mody wrote: > On Thu, Jan 2, 2014 at 11:06 PM, Ned Batchelder > wrote: > > On 1/2/14 12:05 PM, Rustom Mody wrote: > > > >> > >> i'm not sure about this but isnt it normally the cas

Re: About some problem

2014-01-02 Thread Rustom Mody
On Thu, Jan 2, 2014 at 11:06 PM, Ned Batchelder wrote: > On 1/2/14 12:05 PM, Rustom Mody wrote: > >> >> i'm not sure about this but isnt it normally the case that different >> version modules dont get mixed up like that? >> IOW if pytesser was a properly packaged 2.7 module would python 3 be >> ab

Re: About some problem

2014-01-02 Thread Ned Batchelder
On 1/2/14 12:05 PM, Rustom Mody wrote: i'm not sure about this but isnt it normally the case that different version modules dont get mixed up like that? IOW if pytesser was a properly packaged 2.7 module would python 3 be able to get at it ?? If you use a Python 3 installer it can succeed at

Re: About some problem

2014-01-02 Thread Mark Lawrence
On 02/01/2014 16:53, Joel Goldstick wrote: On Thu, Jan 2, 2014 at 11:31 AM, raj kumar mailto:rajkumar84...@gmail.com>> wrote: Hello, I am beginner to python and i am writing following code from pytesser import * and i am getting an error as follow Traceback (most recent cal

Re: About some problem

2014-01-02 Thread Rustom Mody
On Thu, Jan 2, 2014 at 10:23 PM, Joel Goldstick wrote: > > > > On Thu, Jan 2, 2014 at 11:31 AM, raj kumar wrote: >> >> Hello, I am beginner to python and i am writing following code >> >> from pytesser import * >> >> and i am getting an error as follow >> >> Traceback (most recent call last): >>

Re: About some problem

2014-01-02 Thread Joel Goldstick
On Thu, Jan 2, 2014 at 11:31 AM, raj kumar wrote: > Hello, I am beginner to python and i am writing following code > > from pytesser import * > > and i am getting an error as follow > > Traceback (most recent call last): > File "", line 1, in > File "C:\Python33\lib\site-packages\pytesser.py