| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
I haven't had time to test this much, but this allows MapScript to
build and run against Python 3.4. The changes appear to continue to
work with Python 2.7.
If there are multiple Python versions installed on your machine,
the Python version that is selected is whatever CMake finds first
or the path set with -DPYTHON_EXECUTABLE=
Changes include:
* print "" ---> print("")
* raise E, "text" ---> raise E("text")
* PyString_FromStringAndSize() ---> PyBytes_FromStringAndSize()
* Remove references to PyFile*
|
There is also an open ticket for Python3 support: ticket #4748 |
Sorry, something went wrong.
|
I tried this, but I also needed the other setup.py changes made in #4748 (dict, readme) |
Sorry, something went wrong.
|
when i try it out with python3 i get the usual ... even tried to manually edit all the hex_version>= 0x03000 conditions to always be true in mapscriptPYTHON_wrap.c (linux) ImportError: dynamic module does not define init function (PyInit__mapscript) |
Sorry, something went wrong.
|
So where are we at with this pull request? It's a little dated and should be based against master and not the 7.0 branch. --Steve |
Sorry, something went wrong.
|
Beautiful - anyone else want to comment or test? Otherwise I say we merge it and deal with issues as part of the release process. --Steve |
Sorry, something went wrong.
|
I didn't actually end up using this, so I don't have any specific comments/test cases. Glad to see @claudep pick it up. (This PR was fallout of experimenting with options for moving beyond MapScript/PHP 5 for GeoMoose 3, but the final decision was to use a combination of standard WFS calls and client side processing rather than MapScript.) |
Sorry, something went wrong.
|
I'm going to close with with the newer pull request in play. --Steve |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
I haven't had time to test this much, but this allows MapScript to
build and run against Python 3.4. The changes appear to continue to
work with Python 2.7. I kind of accidentally figured this out while playing
around so it may be incomplete, but I figured I'd share it as it is at least a
good start.
If there are multiple Python versions installed on your machine,
the Python version that is selected is whatever CMake finds first
or the path set with -DPYTHON_EXECUTABLE=
Changes include: