jeffreywugz / pyev

Automatically exported from code.google.com/p/pyev
0 stars 0 forks source link

Decorate #-only lines in setup.py are incompatible with Python 3 #20

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. virtualenv venv -p python3.2
2. source venv/bin/activate
3. pip install svn+http://pyev.googlecode.com/svn/trunk/pyev

What is the expected output? What do you see instead?

Expect pyev to install. Instead, you get:

Downloading/unpacking svn+http://pyev.googlecode.com/svn/trunk/pyev
  Checking out http://pyev.googlecode.com/svn/trunk/pyev to /tmp/pip-2oai7g-build
  Running setup.py egg_info for package from svn+http://pyev.googlecode.com/svn/trunk/pyev
    Traceback (most recent call last):
      File "<string>", line 16, in <module>
      File "/tmp/pip-2oai7g-build/setup.py", line 1
        ################################################################################
          ^
    SyntaxError: invalid character in identifier
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):

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

  File "/tmp/pip-2oai7g-build/setup.py", line 1

    ################################################################################

      ^

SyntaxError: invalid character in identifier

----------------------------------------
Command python setup.py egg_info failed with error code 1 in 
/tmp/pip-2oai7g-build
Storing complete log in /home/philip/.pip/pip.log

What version of the product are you using? On what operating system?

Latest version from source, on Ubuntu 12.04 LTS.

Please provide any additional information below.

Would like some non-broken way to install pyev via pip into a series of tox 
virtual environments spanning Python versions 2.6-3.3. The 2.X versions install 
without errors.

Original issue reported on code.google.com by Campadre...@gmail.com on 14 Mar 2013 at 10:37

GoogleCodeExporter commented 9 years ago
I experience the same problem in Ubuntu 13.10

#####
Downloading/unpacking pyev
  Downloading pyev-0.9.0.tar.gz (223kB): 223kB downloaded
  Running setup.py egg_info for package pyev
    Traceback (most recent call last):
      File "<string>", line 16, in <module>
      File "/home/julio/pyvirt/build/pyev/setup.py", line 56, in <module>
        check_version(python_version, min_python_versions[major], "Python{0}".format(major))
      File "/home/julio/pyvirt/build/pyev/setup.py", line 40, in check_version
        if StrictVersion(current_version) < StrictVersion(minimum_version):
      File "/usr/lib/python2.7/distutils/version.py", line 40, in __init__
        self.parse(vstring)
      File "/usr/lib/python2.7/distutils/version.py", line 107, in parse
        raise ValueError, "invalid version number '%s'" % vstring
    ValueError: invalid version number '2.7.5+'
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):

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

  File "/home/julio/pyvirt/build/pyev/setup.py", line 56, in <module>

    check_version(python_version, min_python_versions[major], "Python{0}".format(major))

  File "/home/julio/pyvirt/build/pyev/setup.py", line 40, in check_version

    if StrictVersion(current_version) < StrictVersion(minimum_version):

  File "/usr/lib/python2.7/distutils/version.py", line 40, in __init__

    self.parse(vstring)

  File "/usr/lib/python2.7/distutils/version.py", line 107, in parse

    raise ValueError, "invalid version number '%s'" % vstring

ValueError: invalid version number '2.7.5+'

----------------------------------------
Cleaning up...
Command python setup.py egg_info failed with error code 1 in 
/home/julio/pyvirt/build/pyev
Storing complete log in /home/julio/.pip/pip.log

#####

Original comment by jmolin...@gmail.com on 29 Dec 2013 at 5:48

GoogleCodeExporter commented 9 years ago
jmolinaso, I think that you are actually encountering a different problem, 
which is described in https://code.google.com/p/pyev/issues/detail?id=21

Original comment by msabr...@gmail.com on 24 Mar 2014 at 3:31