Missing version.py.in in source tarball

Issue #319 closed
Tommy Sparber created an issue

installing pygame from the latest source tarball (1.9.2) is missing the version.py.in file required by setup.py.

$ python setup.py install
Traceback (most recent call last):
  File "setup.py", line 294, in <module>
    write_version_module(METADATA['version'], revision)
  File "setup.py", line 286, in write_version_module
    with open('version.py.in', 'r') as header_file:
IOError: [Errno 2] No such file or directory: 'version.py.in'

Is there another preferred method to install from source?

Comments (15)

  1. Tommy Sparber reporter

    Thanks for fixing it. Are you going to update the 1.9.2 sdist tarballs? it is of course not "nice" to update released files without changing version number, but they are currently kind of broken/useless anyways :)

  2. Thomas Kluyver

    PyPI doesn't let you replace files once they're uploaded, so it won't be fixed for 1.9.2. I recommend using the tarball from Bitbucket - this is more truthfully the source tarball, in any case.

    I'd like to get builds working for Python 3.6 once it's out later this month, and then do 1.9.3.

  3. Tommy Sparber reporter

    Thanks for the info. I noticed homebrew deprecated the homebrew-python tap and thus deleted the pygame formula. I think this is ok, as using the wheel is also a good solution. They kept and migrated some formulas, that are not so easily installed using pip. Thus installing using brew is not possible anymore.

    More about this deprecation: https://github.com/Homebrew/homebrew-core/pull/9193

  4. Thomas Kluyver

    That's a bit of a shame, as OSX is the platform which has given us the most problems with the wheel builds. On the plus side, I guess it means more impetus for people to find and fix problems with them.

  5. René Dudfield

    Oh well. I know lots of people on OSX were using the homebrew builds. I guess the travisci builds of pygame will still work for OSX because they just used the dependencies of pygame (libsdl etc).

  6. Log in to comment