Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update shapely to 1.6.4.post1 #46

Merged
merged 2 commits into from
Jul 4, 2018

Conversation

pyup-bot
Copy link
Collaborator

This PR updates Shapely from 1.5.17.post1 to 1.6.4.post1.

Changelog

1.6.3

------------------

- AttributeError is no longer raised when accessing __geo_interface__ of an
empty polygon (450).
- ``asShape`` now handles empty coordinates in mappings as ``shape`` does
(542). Please note that ``asShape`` is likely to be deprecated in a future
version of Shapely.
- Check for length of LineString coordinates in speed mode, preventing crashes
when using LineStrings with only one coordinate (546).

1.6.2

------------------

- Handle a ``TypeError`` that can occur when geometries are torn down (473,
528).
- Splitting a linestring by one of its end points will now succeed instead of
failing with a ``ValueError`` (524, 533).
- Missing documentation of a geometry's ``overlaps`` predicate has been added
(522).

1.6.1

------------------

- Avoid ``STRTree`` crashes due to dangling references (505) by maintaining
references to added geometries.
- Reduce log level to debug when reporting on calls to ctypes ``CDLL()`` that
don't succeed and are retried (515).
- Clarification: applications like GeoPandas that need an empty geometry object
should use ``BaseGeometry()`` instead of ``Point()`` or ``Polygon()``. An
``EmptyGeometry`` class has been added in the master development branch and
will be available in the next non-bugfix release.

1.6.0

functions (``split()`` and ``polylabel()``) to the shapely.ops module.
Exceptions are consolidated in a shapely.errors module and logging practices
have been improved. Shapely's optional features depending on Numpy are now
gathered into a requirements set named "vectorized" and these may be installed
like ``pip install shapely[vectorized]``.

Much of the work on 1.6.0 was aimed to improve the project's build and
packaging scripts and to minimize run-time dependencies. Shapely now vendorizes
packaging to use during builds only and never again invokes the geos-config
utility at run-time.

In addition to the changes listed under the alpha and beta pre-releases below,
the following change has been made to the project:

- Project documentation is now hosted at 
https://shapely.readthedocs.io/en/latest/.

Thank you all for using, promoting, and contributing to the Shapely project.

1.6b5

------------------

Bug fixes:

- Passing a single coordinate to ``LineString()`` with speedups disabled now
raises a ValueError as happens with speedups enabled. This resolves 509.

1.6b4

------------------

Bug fixes:

- Isolate vendorized packaging in a _vendor directory, remove obsolete
dist-info, and remove packaging from project requirements (resolves 468).

1.6b3

------------------

Bug fixes:

- Level for log messages originating from the GEOS notice handler reduced from
WARNING to INFO (447).
- Permit speedups to be imported again without Numpy (444).

1.6b2

------------------

New features:

- Add support for GeometryCollection to shape and asShape functions (422).

1.6b1

------------------

Bug fixes:

- Implemented __array_interface__ for empty Points and LineStrings (403).

1.6a3

------------------

Bug fixes:

- Remove accidental hard requirement of Numpy (431).

Packaging:

- Put Numpy in an optional requirement set named "vectorized" (431).

1.6a2

------------------

Bug fixes:

- Shapely no longer configures logging in ``geos.py`` (415).

Refactoring:

- Consolidation of exceptions in ``shapely.errors``.
- ``UnsupportedGEOSVersionError`` is raised when GEOS < 3.3.0 (407).

Packaging:

- Added new library search paths to assist Anaconda (413).
- geos-config will now be bypassed when NO_GEOS_CONFIG env var is set. This
allows configuration of Shapely builds on Linux systems that for whatever
reasons do not include the geos-config program (322).

1.6a1

------------------

New features:

- A new error derived from NotImplementedError, with a more useful message, is
raised when the GEOS backend doesn't support a called method (216).
- The ``project()`` method of LineString has been extended to LinearRing
geometries (286).
- A new ``minimum_rotated_rectangle`` attribute has been added to the base
geometry class (354).
- A new ``shapely.ops.polylabel()`` function has been added. It
computes a point suited for labeling concave polygons (395).
- A new ``shapely.ops.split()`` function has been added. It splits a
geometry by another geometry of lesser dimension: polygon by line, line by
point (293, 371).
- ``Polygon.from_bounds()`` constructs a Polygon from bounding coordinates
(392).
- Support for testing with Numpy 1.4.1 has been added (301).
- Support creating all kinds of empty geometries from empty lists of Python
objects (397, 404).

Refactoring:

- Switch from ``SingleSidedBuffer()`` to ``OffsetCurve()`` for GEOS >= 3.3
(270).
- Cython speedups are now enabled by default (252).

Packaging:

- Packaging 16.7, a setup dependency, is vendorized (314).
- Infrastructure for building manylinux1 wheels has been added (391).
- The system's ``geos-config`` program is now only checked when ``setup.py``
is executed, never during normal use of the module (244).
- Added new library search paths to assist PyInstaller (382) and Windows
(343).
Links

@coveralls
Copy link

Pull Request Test Coverage Report for Build 125

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 1 unchanged line in 1 file lost coverage.
  • Overall coverage decreased (-0.01%) to 59.432%

Files with Coverage Reduction New Missed Lines %
pymaid/fetch.py 1 71.91%
Totals Coverage Status
Change from base Build 110: -0.01%
Covered Lines: 4203
Relevant Lines: 7072

💛 - Coveralls

@schlegelp schlegelp merged commit f82c889 into master Jul 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants