can't install on python 3

Bug #906007 reported by Mike Bayer
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
oursql
New
Undecided
Unassigned

Bug Description

the current py3k release of OurSQL seems to be a Win32 .exe file.

Currently there's no obvious way to install OurSQL on Py3K and documentation should be added for what release/where/how. There's no "Python :: 3" classifier up at http://pypi.python.org/pypi/oursql/0.9.3 so that is also a bug, if OurSQL supports Py3K.

A naive "pip install oursql" in Python 3 produces:

classics-MacBook-Pro:Downloads classic$ /Library/Frameworks/Python.framework/Versions/3.2/bin/pip install --upgrade oursql
Downloading/unpacking oursql
  Downloading oursql-0.9.3.linux-i686.tar.gz (210Kb): 210Kb downloaded
  Running setup.py egg_info for package oursql
    Traceback (most recent call last):
      File "<string>", line 14, in <module>
    IOError: [Errno 2] No such file or directory: '/Users/classic/Downloads/build/oursql/setup.py'
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):

  File "<string>", line 14, in <module>

IOError: [Errno 2] No such file or directory: '/Users/classic/Downloads/build/oursql/setup.py'

----------------------------------------
Command python setup.py egg_info failed with error code 1
Storing complete log in /Users/classic/.pip/pip.log

(actually python 2 seems to be doing it too at the moment....)

Revision history for this message
Stephen Thorne (jerub) wrote :

It looks like the linux build I uploaded is not well liked by pip, so I've removed that and linux users will have to compile from source.

Pypi does not provide a nice way of providing a different archive for python2 or python3 - indeed, the current release on pypi is 0.9.3 for python2. I only merged and cut 0.9.3 for python3 today, and looking into the documentation I don't see a clear way of providing both python2 and python3 source archives.

Revision history for this message
Benjamin Bach (benjaoming) wrote :

I have the same issues, namely because the setup.py file has some really basic Python 3 compat mistakes.. here's a diff that fixes it:

53c53
< print("cython not found, using previously-cython'd .c file.")
---
> print "cython not found, using previously-cython'd .c file."
89c89
< print(' '.join(args))
---
> print ' '.join(args)
93c93
< print('failed to execute', args[0])
---
> print 'failed to execute', args[0]
96c96
< return split_quoted(str(stdout).strip())
---
> return split_quoted(stdout.strip())

Revision history for this message
Stephen Thorne (jerub) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.