Skip to content

Commit 5523538

Browse files
author
Marc Garcia
committed
Adding pyntxos sprint
1 parent d7d202c commit 5523538

File tree

1 file changed

+69
-0
lines changed

1 file changed

+69
-0
lines changed

_posts/2019-08-07-pyntxos.md

Lines changed: 69 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,69 @@
1+
---
2+
category: "london"
3+
title: "Pyntxos - Scraping, visualization, optimizationa and dashboarding"
4+
level: "All levels"
5+
time: "18:00"
6+
rsvp_link: https://www.meetup.com/Python-Sprints/events/263261166/
7+
project:
8+
sponsor: quantum_black
9+
---
10+
11+
![](https://tesis2012.files.wordpress.com/2012/03/pintxos_bar.jpg)
12+
13+
In this sprint we will build a new project, [Pyntxos](https://github.com/python-sprints/pyntxos).
14+
15+
Some context... [EuroSciPy 2019](https://www.euroscipy.org/2019/) will be in September in Bilbao, Spain.
16+
Besides a great [program](https://www.euroscipy.org/2019/program.html) of tutorials, talks,
17+
[maintainers sessions](https://www.euroscipy.org/2019/maintainers.html) and sprints, the conference will
18+
have social activities and networking.
19+
20+
What EuroSciPy will have different from other conferences, is that being in Bilbao, part of the networking
21+
will be done in their traditional [pintxo routes](https://en.wikipedia.org/wiki/Pincho). Pintxos are small
22+
portion of food, usually served on top of a small slice of break. There are streets full of pintxo restaurants,
23+
and what is usual is to eat a pintxo in one (with a small glass of wine or beer), socialize standing in the
24+
restaurant or the street for a while, and then go for the next, and keep repeating, following a route.
25+
26+
EuroPython 2015 and 2016 were hosted in Bilbao, and pintxo routes became very popular.
27+
[This article](http://travel.cnn.com/san-sebastians-amazing-street-michelin-experience-736551/)
28+
gives some information about the importance of gastronomy in the Basque country.
29+
30+
It would be easy to just decide the street or area where EuroSciPy participants should go, so
31+
is easy for people to network with other EuroSciPy participants. That would be easy, but not as fun as
32+
overcomplicating things and build a Python project to "optimise" and visualize pintxo routes.
33+
34+
In this sprint we will build a new open source Python project. This will allow participants to learn
35+
how to contribute to open source projects, and the different components of a project:
36+
37+
- API design
38+
- Source code
39+
- Tests
40+
- Documentation
41+
- Linting
42+
- Continuous Integration
43+
- Benchmarks
44+
- Packaging
45+
46+
And at the same time, we will work and learn some open source libraries for data scraping, analysis,
47+
visualization, and dashboarding. Some of the proposed ones are:
48+
49+
- [jupyter](https://jupyter.org/)
50+
- [ipywidgets](https://ipywidgets.readthedocs.io/en/stable/)
51+
- [scrapy](https://scrapy.org/)
52+
- [pandas](https://pandas.pydata.org)
53+
- [geopandas](http://geopandas.org/)
54+
- [http://geoviews.org/](http://geoviews.org/)
55+
- [voila](https://github.com/QuantStack/voila)
56+
57+
Agenda
58+
59+
- 6pm: Networking, drinks and food
60+
- 6:30pm: Project presentation and team creation
61+
- 6:45pm: Coding
62+
- 9pm: Group presentations
63+
- 9:30pm: End of the event, or pub
64+
65+
Requirements
66+
67+
- Bring a laption with Anaconda and git installed
68+
69+
**Gitter channel:** [https://gitter.im/py-sprints/pyntxos](https://gitter.im/py-sprints/pyntxos)

0 commit comments

Comments
 (0)