fixing readme, 0.5.5

mvexel · Aug 21, 2016 · 134b3ff · 134b3ff
1 parent cfb9407
commit 134b3ff
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 4 deletions.
diff --git a/README.md b/README.md
@@ -31,7 +31,8 @@ could do this for example:
 
 ```python
 print [(feature['tags']['name'], feature['id']) for feature in response['elements']]
-[(u'Salt Lake City', 150935219), (u'Salt Lake City', 585370637), (u'Salt Lake City', 1615721573)]```
+[(u'Salt Lake City', 150935219), (u'Salt Lake City', 585370637), (u'Salt Lake City', 1615721573)]
+```
 
 You can specify the format of the response. By default, you will get GeoJSON using the `responseformat` parameter. Alternatives are plain JSON (`json`) and OSM XML (`xml`), as ouput directly by the Overpass API.
 
@@ -81,7 +82,8 @@ to the constructor:
 
 ```python
 map_query = overpass.MapQuery(50.746,7.154,50.748,7.157)
-response = api.Get(map_query)```
+response = api.Get(map_query)
+```
 
 #### WayQuery
 
@@ -91,7 +93,8 @@ constructor:
 
 ```python
 way_query = overpass.WayQuery('[name="Highway 51"]')
-response = api.Get(way_query)```
+response = api.Get(way_query)
+```
 
 ## Testing
 

diff --git a/setup.py b/setup.py
@@ -11,7 +11,7 @@
 setup(
     name='overpass',
     packages=['overpass'],
-    version='0.5.4',
+    version='0.5.5',
     description='Python wrapper for the OpenStreetMap Overpass API',
     long_description=long_description,
     author='Martijn van Exel',