EuroPython 2016 remarks

Last week, Eu­ro­P­y­thon 2016 fi­nis­he­d, and it was an ama­zing con­fe­ren­ce I had the plea­su­re to atten­d. He­re is my re­view of tho­se da­ys.

The conference

I arri­ved on Satur­day noon at Bil­bao, Spai­n, the day be­fo­re the con­fe­ren­ce, so I had so­me ti­me to kno­w ­the ci­ty, see the ve­nues, etc. The next da­y, on Sun­da­y, was for two se­pa­ra­te wo­rks­hop­s: Djan­go girls an­d ­Be­gin­ne­r’s da­y. I atten­ded the be­gin­ne­r’s day as a co­ach, and hel­ped a group of in­ter­me­dia­te de­ve­lo­pers wi­th se­ve­ral exer­ci­ses ai­med at ex­plai­ning so­me Py­thon con­cep­ts, su­ch as: con­text ma­na­ger­s, de­co­ra­tor­s, ­ma­gic me­tho­d­s, ge­ne­ra­tor­s, etc. It was rea­lly cu­rious that so­me of the­se to­pi­cs we­re tho­se I was going to co­ve­r on my ta­lk on Wed­nes­da­y, so I felt rea­lly glad about tha­t. I took an oa­th (ve­ry funny BTW) for be­co­ming a be­gin­ne­r’s men­to­r, and so I di­d (it was rea­lly good ac­tua­ll­y). I had a great ti­me hel­ping other de­ve­lo­per­s, ex­chan­ging ideas and ex­pe­rien­ces du­ring lun­ch, ­sol­ving pro­ble­ms, and ge­tting a first glimp­se on what the con­fe­ren­ce was going to be like.

../ep2016-beginners-mentor-oath.png

The mo­ment of the oa­th for be­co­ming a men­to­r, and ear­ning the ba­dge.

After the wo­rks­hop fi­nis­he­d, I wa­lked to the main ve­nue, and ga­ve a hand pa­cking the bags of the con­fe­ren­ce. After tha­t, ti­me to­ ­see around Bil­bao.

From Mon­day to Fri­day was the con­fe­ren­ce itsel­f, wi­th all the ta­lks, and tra­i­nings.

Mon­day started wi­th the in­tro­duc­tion to the con­fe­ren­ce, and shor­tly the­rea­fte­r, the ve­ry first ke­y­no­te by Ra­chel Wi­ll­me­r, who ga­ve a great pre­sen­ta­tio­n, sha­ring a lot of ex­pe­rien­ce, and in­te­res­ting idea­s.

At around noon the­re was a ke­y­no­te by N. To­ller­vey about Mi­cro­P­y­tho­n. The pre­sen­ta­tion was ex­ce­llent (o­ne of the ones I liked the mos­t), and the idea of the pro­ject is awe­so­me. On top of tha­t, it was an­noun­ced that the BBC wa­s ­gi­ving away mi­cro­:­bi­ts for the atten­dees of ­the con­fe­ren­ce, so it was a great sur­pri­se to pi­ck up mi­ne at the con­fe­ren­ce desk. I even started pla­ying around a bit wi­th it (mo­re in a fu­tu­re pos­t).

The rest of the after­noon, I atten­ded se­ve­ral ta­lks. At the en­d, the­re we­re, of cour­se the li­gh­tning ta­lks, whi­ch we­re ama­zin­g.

Tues­day started wi­th the ke­y­no­te by P. Hil­de­bran­t, pre­sen­ting how Dis­ney uses se­ve­ral te­ch­no­lo­gie­s, in­clu­ding Py­tho­n, as su­pport for mo­vies and pro­duc­tion­s. It was ve­ry good and en­li­gh­ten­ing to see an en­dea­vour of su­ch ex­tent wi­th Py­tho­n. A­fter tha­t, du­ring mor­ning I atten­ded a wo­rks­hop about As­ync web de­ve­lo­p­men­t, wi­th se­ve­ral Py­thon te­ch­no­lo­gie­s ­for doing as­yn­ch­ro­nous com­pu­ta­tion.

Du­ring the after­noon, I wa­tched se­ve­ral great ta­lks, in­clu­ding “Pro­tect you users wi­th Cir­cuit Breaker­s”, an­d se­ve­ral other good ones, clo­sing wi­th the li­gh­tning ta­lks.

Wed­nes­day was the day of my ta­lk, so I atten­ded so­me ta­lks du­ring mor­ning and then, at the after­noon, I pre­sen­ted mi­ne. I rea­lly liked how it de­ve­lo­pe­d. Mo­reo­ve­r, it was rea­lly good to re­cei­ve good fee­dba­ck from so­me atten­dees, sa­ying the­y ­liked it, and that it was use­ful for the­m. Shor­tly the­rea­fte­r, I pu­blis­hed the sli­des and the sour­ce co­de.

On Thurs­da­y, the­re we­re so­me ta­lks about as­yn­c/await and as­yn­ch­ro­nous pro­gra­m­ming in Py­thon 3, mo­cks, and hi­gh-a­vai­la­bi­li­ty ar­chi­tec­tu­re.

On Fri­da­y, the ke­y­no­te was about how Py­thon is us­ed by the scien­ti­fic co­m­mu­ni­ty. It was ve­ry en­li­gh­ten­in­g, and in­te­res­tin­g ­to see ano­ther use ca­se of Py­tho­n, and how is be­co­ming the main te­ch­no­lo­gy on this area.

The ta­lks du­ring mor­ning in this ca­se, we­re di­vi­ded among se­ve­ral to­pi­cs, being the main ones: ins­tru­men­ta­tion for per­for­man­ce ­me­tri­cs, “How to mi­gra­te form Pos­tgreS­QL to HDF5 and li­ve ha­ppi­ly ever afte­r”, “S­plit Up! Fi­gh­ting the mo­n­oli­th”. Du­ring the after­noon, I joi­ned a wo­rks­hop about Do­cke­r, on whi­ch we built an appli­ca­tion using Do­cke­r-­com­bi­ne, and fo­llo­wed good prac­ti­ce­s.

It is wor­th men­tio­nin­g, that on Fri­day the­re was an spe­cial edi­tion for li­gh­tning ta­lks, whi­ch was not in the ori­gi­nal sche­du­le. Afte­r ­making so­me arran­ge­men­ts, and due to so­me on-­the-­fly chan­ges, it was po­s­si­ble to ha­ve ano­ther ses­sion for li­gh­tning ta­lks, ri­ght be­fo­re ­the sprin­ts orien­ta­tion and the clo­sing ses­sio­n.

Satur­day and Sun­day we­re for sprin­ts (ha­cka­thon­s). On Satur­day I joi­ned to sprint on aioh­ttp, and ac­tua­ll­y ­su­bmi­tted a pu­ll re­quest, tha­t was mer­ge­d, whe­reas on Sun­day I wanted to che­ck on a py­test is­sue.

My talk

It was great to ha­ve the oppor­tu­ni­ty to pre­sent at Eu­ro­P­y­tho­n. What was even be­tte­r, was the po­si­ti­ve fee­dba­ck I got from other atten­dees, and the fact that it was use­ful and in­te­res­ting for them (whi­ch wa­s, in the en­d, what I ca­red most abou­t). I found the ex­pe­rien­ce ve­r­y ­po­si­ti­ve.

From the co­m­men­ts, I ga­the­red so­me­thing I ha­ve not no­ti­ced when I first en­vi­sio­ned the ta­lk, whi­ch is how use­ful the­se con­cep­ts mi­gh­t ­be for peo­ple using Py­thon for scien­ti­fic appli­ca­tion­s. It see­ms, scien­tis­ts using Py­thon for da­ta pro­ce­s­sing or com­pu­ta­tio­n, do no­t u­sua­lly ha­ve the ba­ck­ground of a de­ve­lo­pe­r, so con­cep­ts like co­de rea­da­bi­li­ty, te­ch­ni­cal deb­t, and main­tai­na­bi­li­ty, are hel­pful in or­de­r ­to im­pro­ve the co­de ba­se. This ga­ve me the idea of adap­ting the exam­ple­s, perhaps adding one re­lated to the­se area­s.

Python use cases

The­re we­re peo­ple from many coun­trie­s, in­dus­trie­s, and com­pa­nies wi­th di­ffe­rent ba­ck­groun­d­s. The trend see­ms to be now on ­da­ta scien­ce, but Py­thon is wi­de­ly us­ed in many area­s.

I be­lie­ve the main areas of fo­cus for Py­thon are: so­ftwa­re de­ve­lo­p­men­t, sys­tem ad­mi­nis­tra­tion / Dev Op­s, and scien­ce.

The­re we­re ta­lks, tra­cks, ses­sion­s, and tra­i­nings for all of the­m, wi­th ve­ry te­ch­ni­cal de­tai­l.

Highlights

The­re we­re so many great ta­lks and re­sour­ces that I can­not na­me ea­ch sin­gle one of the­m, so I wi­ll point the mai­n ­to­pi­cs and so­me of the ta­lks that gra­bbed my atten­tion the mos­t, but plea­se keep in mind that all we­re grea­t.

Among the many things pen­ding to test and re­sear­ch, are al­so books. I lear­ned about PY­RO­4, for ma­na­ging Py­thon re­mo­te ob­jec­ts, whi­ch see­ms like a pro­mi­sing te­ch­no­lo­g­y. I wi­ll di­ve in­to mo­re de­tail on con­da and the buil­ding sys­te­ms, con­da ­chan­nel­s, etc. The ta­lk “Ex­plo­ring your Py­thon in­ter­pre­te­r” was rea­lly in­te­res­tin­g, and it was a good in­tro­duc­tio­n, in or­de­r ­to be­co­me in­vol­ved wi­th CP­y­thon de­ve­lo­p­men­t.

I atten­ded many ta­lks about the la­test fea­tu­res of Py­thon 3.5, su­ch as as­yn­cIO, co­rou­ti­nes, and all the new func­tio­na­li­ties fo­r a­s­yn­ch­ro­nous pro­gra­m­min­g, and they all we­re rea­lly in­te­res­tin­g. In par­ti­cu­lar “The re­port of Twis­te­d’s Dea­th” was ve­ry in­te­res­tin­g, an­d (s­poi­ler aler­t), it looks like sti­ll has an in­te­res­ting fu­tu­re com­pe­ting wi­th the new li­bra­ries and stan­dar­d­s.

On the li­gh­tning ta­lks, it was pre­sen­ted a re­ver­se de­bu­gger (re­v­db), and its de­mo was ama­zin­g.

Conclusion

After atten­ding many ta­lks, and tra­i­nings, ta­lking to many other ex­pe­rien­ce de­ve­lo­per­s, sys­tem ad­mi­nis­tra­tor­s, and da­ta scien­tis­ts, I can sta­te that the con­fe­ren­ce has an ama­zing lear­ning en­vi­ron­men­t, and the ou­tco­me was com­ple­te­ly po­si­ti­ve. It was use­fu­l ­for ca­tching up wi­th te­ch­no­lo­g­y, che­cking the en­vi­ron­ment and see how Py­thon is being us­ed or de­plo­yed in the wil­d, learn fro­m u­se ca­ses, ex­pe­rien­ce­s, and ex­chan­ge idea­s.

The con­tent was rea­lly ins­pi­ring and open-­min­din­g. I ha­ve lo­ts of ite­ms to che­ck, as poin­ts for re­sear­ch, whi­ch I wi­ll co­ver in fo­llo­win­g en­trie­s.

Py­thon 3 is mu­ch mo­re wi­de­ly us­ed than one would ex­pec­t. It is ac­tua­lly the stan­dard no­w, and many ta­lks (in­clu­ding mi­ne), we­re using Py­thon 3 ­co­de, but most im­por­tan­tl­y, most pro­jec­ts are now in this ver­sio­n, whe­reas Py­thon 2 looks like the le­ga­cy op­tio­n. Good news :-)

All in all, this edi­tion of Eu­ro­P­y­thon was awe­so­me, and I am looking fo­rward to pre­sen­ting again next yea­r!