[Community] Shapely for python 3.x

[Uroš Bernik]

Hello

Anyone knows if Shapely for python 3.x is coming out soon? I tried fiddling with the port using 2to3 but there are some problems, and i need to make some decisions about the production workstations we'll be using

Thanx

[Uroš Bernik]

Okay, found a solution, a github repo with the port exists and works. Without the speedups though. If someone else needs it, please reply.

On 23. avg. 2013, at 15:01, Uro? Bernik <uros.bernik at siol.net> wrote:

Hello

Anyone knows if Shapely for python 3.x is coming out soon? I tried fiddling with the port using 2to3 but there are some problems, and i need to make some decisions about the production workstations we'll be using

Thanx

[Sean Gillies]

I intend that Mike's (mwtoews) branch will become the new Shapely 1.3.
Details at:

https://github.com/Toblerity/Shapely/issues/56

Post by Uroš Bernik
Okay, found a solution, a github repo with the port exists and works.
Without the speedups though. If someone else needs it, please reply.
Hello
Anyone knows if Shapely for python 3.x is coming out soon? I tried
fiddling with the port using 2to3 but there are some problems, and i need
to make some decisions about the production workstations we'll be using
Thanx
_______________________________________________
Community mailing list
Community at lists.gispython.org
http://lists.gispython.org/mailman/listinfo/community
_______________________________________________
Community mailing list
Community at lists.gispython.org
http://lists.gispython.org/mailman/listinfo/community

[Uroš Bernik]

Yes, that is the one i found. Thanks for the reply anyway.

On 26. avg. 2013, at 20:35, Sean Gillies <sean.gillies at gmail.com> wrote:

I intend that Mike's (mwtoews) branch will become the new Shapely 1.3. Details at:

https://github.com/Toblerity/Shapely/issues/56

Post by Uroš Bernik
Okay, found a solution, a github repo with the port exists and works. Without the speedups though. If someone else needs it, please reply.
Hello
Anyone knows if Shapely for python 3.x is coming out soon? I tried fiddling with the port using 2to3 but there are some problems, and i need to make some decisions about the production workstations we'll be using
Thanx
_______________________________________________
Community mailing list
Community at lists.gispython.org
http://lists.gispython.org/mailman/listinfo/community
_______________________________________________
Community mailing list
Community at lists.gispython.org
http://lists.gispython.org/mailman/listinfo/community

[Mike Toews]

Post by Sean Gillies
I intend that Mike's (mwtoews) branch will become the new Shapely 1.3.
https://github.com/Toblerity/Shapely/issues/56

It looks like there are folks looking to have Python 3 support (e.g.
https://github.com/SciTools/cartopy/pull/308). How should we proceed?
I have two branches on the go, so let me describe them.

py3: https://github.com/mwtoews/shapely/commits/py3

I initially had a `py3` branch, which had the minimal changes to
support both Python 2 and 3 from a single code base. The biggest
change here, besides the obvious, is the switch in setup.py from
setuptools to distutils. (Somehow, another branch of mine, `v13`,
slipped into this branch for a few weeks up until now.. sorry if you
pulled this and it is different. Admittedly, I'm still learning the
dark art of git, which I also used to restore the branch to an
intended previous state, plus merging the latest commits from upstream
master.) This branch should be the prime place for testing to make
sure most of the Python 2/3 features work. For instance, do speedups
work for everyone?

v13: https://github.com/mwtoews/shapely/commits/v13

The `v13` branch is a somewhat parallel branch to implement some more
aggressive changes for version 1.3, including reader/writer classes
for WKT/WKB formats, use of GEOS version numbers (rather than C API
version numbers) to determine capabilities, and a few other things.
(At present, it is a few commits behind upstream master, but I can
merge this). The wkt output is different from this branch, and I'd
like to do some more testing to see if the performance is
good/reliable.

Furthermore, with both branches I'm using Travis CI to do an automated
QA/QC, which are mostly looking good. Except for some GEOS
functionality mismatches, which can be skipped with some features from
a newer unittest package
(https://github.com/Toblerity/Shapely/issues/70), which are yet to be
committed pending on any comments on the direction of unit tests.

Could I suggest testing/merging py3 this week? Then some parts of v13
after that? As always, please test and communicate anything good/bad
to https://github.com/Toblerity/Shapely/issues/56 otherwise I don't
know if I'm breaking things or not.

-Mike

[Uroš Bernik]

About speedups, when i use setup.py install, in the end theres a message: the c extension could not be compiled, speedups are not enabled. Im running winows 7 64bit on my production machines where i ran the installation. I guess i should compile speedups.c manually using visual studio or something. Otherwise i have had no problems so far.

Post by Sean Gillies
I intend that Mike's (mwtoews) branch will become the new Shapely 1.3.
https://github.com/Toblerity/Shapely/issues/56

It looks like there are folks looking to have Python 3 support (e.g.
https://github.com/SciTools/cartopy/pull/308). How should we proceed?
I have two branches on the go, so let me describe them.

py3: https://github.com/mwtoews/shapely/commits/py3

I initially had a `py3` branch, which had the minimal changes to
support both Python 2 and 3 from a single code base. The biggest
change here, besides the obvious, is the switch in setup.py from
setuptools to distutils. (Somehow, another branch of mine, `v13`,
slipped into this branch for a few weeks up until now.. sorry if you
pulled this and it is different. Admittedly, I'm still learning the
dark art of git, which I also used to restore the branch to an
intended previous state, plus merging the latest commits from upstream
master.) This branch should be the prime place for testing to make
sure most of the Python 2/3 features work. For instance, do speedups
work for everyone?

v13: https://github.com/mwtoews/shapely/commits/v13

The `v13` branch is a somewhat parallel branch to implement some more
aggressive changes for version 1.3, including reader/writer classes
for WKT/WKB formats, use of GEOS version numbers (rather than C API
version numbers) to determine capabilities, and a few other things.
(At present, it is a few commits behind upstream master, but I can
merge this). The wkt output is different from this branch, and I'd
like to do some more testing to see if the performance is
good/reliable.

Furthermore, with both branches I'm using Travis CI to do an automated
QA/QC, which are mostly looking good. Except for some GEOS
functionality mismatches, which can be skipped with some features from
a newer unittest package
(https://github.com/Toblerity/Shapely/issues/70), which are yet to be
committed pending on any comments on the direction of unit tests.

Could I suggest testing/merging py3 this week? Then some parts of v13
after that? As always, please test and communicate anything good/bad
to https://github.com/Toblerity/Shapely/issues/56 otherwise I don't
know if I'm breaking things or not.

-Mike

[Uroš Bernik]

On 27. avg. 2013, at 16:47, Uro? Bernik <uros.bernik at siol.net> wrote:

About speedups, when i use setup.py install, in the end theres a message: the c extension could not be compiled, speedups are not enabled. Im running winows 7 64bit on my production machines where i ran the installation. I guess i should compile speedups.c manually using visual studio or something. Otherwise i have had no problems so far.

Post by Sean Gillies
I intend that Mike's (mwtoews) branch will become the new Shapely 1.3.
https://github.com/Toblerity/Shapely/issues/56

It looks like there are folks looking to have Python 3 support (e.g.
https://github.com/SciTools/cartopy/pull/308). How should we proceed?
I have two branches on the go, so let me describe them.

py3: https://github.com/mwtoews/shapely/commits/py3

I initially had a `py3` branch, which had the minimal changes to
support both Python 2 and 3 from a single code base. The biggest
change here, besides the obvious, is the switch in setup.py from
setuptools to distutils. (Somehow, another branch of mine, `v13`,
slipped into this branch for a few weeks up until now.. sorry if you
pulled this and it is different. Admittedly, I'm still learning the
dark art of git, which I also used to restore the branch to an
intended previous state, plus merging the latest commits from upstream
master.) This branch should be the prime place for testing to make
sure most of the Python 2/3 features work. For instance, do speedups
work for everyone?

v13: https://github.com/mwtoews/shapely/commits/v13

The `v13` branch is a somewhat parallel branch to implement some more
aggressive changes for version 1.3, including reader/writer classes
for WKT/WKB formats, use of GEOS version numbers (rather than C API
version numbers) to determine capabilities, and a few other things.
(At present, it is a few commits behind upstream master, but I can
merge this). The wkt output is different from this branch, and I'd
like to do some more testing to see if the performance is
good/reliable.

Furthermore, with both branches I'm using Travis CI to do an automated
QA/QC, which are mostly looking good. Except for some GEOS
functionality mismatches, which can be skipped with some features from
a newer unittest package
(https://github.com/Toblerity/Shapely/issues/70), which are yet to be
committed pending on any comments on the direction of unit tests.

Could I suggest testing/merging py3 this week? Then some parts of v13
after that? As always, please test and communicate anything good/bad
to https://github.com/Toblerity/Shapely/issues/56 otherwise I don't
know if I'm breaking things or not.

-Mike
_______________________________________________
Community mailing list
Community at lists.gispython.org
http://lists.gispython.org/mailman/listinfo/community

[Uroš Bernik]

Oh and one more thing, i had to manually add geos and geos_c.dll someplace thats also in the system path of course, i just put them to c:\python33\dlls. Since they are not included in the git repo, i downloaded the appropriate egg file for shapely 1.2.18 for py 2.7 for windows 64bit and got them from there. Otherwise shapely would complain about not being able to load these dlls.

Post by Sean Gillies
I intend that Mike's (mwtoews) branch will become the new Shapely 1.3.
https://github.com/Toblerity/Shapely/issues/56

It looks like there are folks looking to have Python 3 support (e.g.
https://github.com/SciTools/cartopy/pull/308). How should we proceed?
I have two branches on the go, so let me describe them.

py3: https://github.com/mwtoews/shapely/commits/py3

I initially had a `py3` branch, which had the minimal changes to
support both Python 2 and 3 from a single code base. The biggest
change here, besides the obvious, is the switch in setup.py from
setuptools to distutils. (Somehow, another branch of mine, `v13`,
slipped into this branch for a few weeks up until now.. sorry if you
pulled this and it is different. Admittedly, I'm still learning the
dark art of git, which I also used to restore the branch to an
intended previous state, plus merging the latest commits from upstream
master.) This branch should be the prime place for testing to make
sure most of the Python 2/3 features work. For instance, do speedups
work for everyone?

v13: https://github.com/mwtoews/shapely/commits/v13

The `v13` branch is a somewhat parallel branch to implement some more
aggressive changes for version 1.3, including reader/writer classes
for WKT/WKB formats, use of GEOS version numbers (rather than C API
version numbers) to determine capabilities, and a few other things.
(At present, it is a few commits behind upstream master, but I can
merge this). The wkt output is different from this branch, and I'd
like to do some more testing to see if the performance is
good/reliable.

Furthermore, with both branches I'm using Travis CI to do an automated
QA/QC, which are mostly looking good. Except for some GEOS
functionality mismatches, which can be skipped with some features from
a newer unittest package
(https://github.com/Toblerity/Shapely/issues/70), which are yet to be
committed pending on any comments on the direction of unit tests.

Could I suggest testing/merging py3 this week? Then some parts of v13
after that? As always, please test and communicate anything good/bad
to https://github.com/Toblerity/Shapely/issues/56 otherwise I don't
know if I'm breaking things or not.

-Mike

[Sean Gillies]

Hi Mike,

I just now fetched py3 and ran the tests (95 pass, 6 fail). Speedups seemed
to work. We'll need to revert to setuptools because I like using its
develop target. I'll follow up in issue 56 or start a new issue this
afternoon.

Post by Mike Toews

Post by Sean Gillies
I intend that Mike's (mwtoews) branch will become the new Shapely 1.3.
https://github.com/Toblerity/Shapely/issues/56

It looks like there are folks looking to have Python 3 support (e.g.
https://github.com/SciTools/cartopy/pull/308). How should we proceed?
I have two branches on the go, so let me describe them.
py3: https://github.com/mwtoews/shapely/commits/py3
I initially had a `py3` branch, which had the minimal changes to
support both Python 2 and 3 from a single code base. The biggest
change here, besides the obvious, is the switch in setup.py from
setuptools to distutils. (Somehow, another branch of mine, `v13`,
slipped into this branch for a few weeks up until now.. sorry if you
pulled this and it is different. Admittedly, I'm still learning the
dark art of git, which I also used to restore the branch to an
intended previous state, plus merging the latest commits from upstream
master.) This branch should be the prime place for testing to make
sure most of the Python 2/3 features work. For instance, do speedups
work for everyone?
v13: https://github.com/mwtoews/shapely/commits/v13
The `v13` branch is a somewhat parallel branch to implement some more
aggressive changes for version 1.3, including reader/writer classes
for WKT/WKB formats, use of GEOS version numbers (rather than C API
version numbers) to determine capabilities, and a few other things.
(At present, it is a few commits behind upstream master, but I can
merge this). The wkt output is different from this branch, and I'd
like to do some more testing to see if the performance is
good/reliable.
Furthermore, with both branches I'm using Travis CI to do an automated
QA/QC, which are mostly looking good. Except for some GEOS
functionality mismatches, which can be skipped with some features from
a newer unittest package
(https://github.com/Toblerity/Shapely/issues/70), which are yet to be
committed pending on any comments on the direction of unit tests.
Could I suggest testing/merging py3 this week? Then some parts of v13
after that? As always, please test and communicate anything good/bad
to https://github.com/Toblerity/Shapely/issues/56 otherwise I don't
know if I'm breaking things or not.
-Mike
_______________________________________________
Community mailing list
Community at lists.gispython.org
http://lists.gispython.org/mailman/listinfo/community