At the beginning of the summer we had a question: “Python-programmers in Minsk exist and this is a fact. But why is there no “interest circle” yet? ” In other words, we wanted to organize a python-community, create monthly meetings, where everyone can make interesting reports and answer equally interesting questions. Of course, all this is accompanied by discussions in an informal setting.
The first mitap was held on June 14 and gathered about 140 people out of 200 declared. Four reports were read in the bite with burgers, which, in fact, can be viewed below.
The report reviewed some basic principles of working with the Python programming language. Simple examples and recommendations for improving the code and optimally solving the simplest tasks are shown.
The main points of the report: • descriptors as powerful mechanisms for managing object attributes; • underestimation of the descriptors in practice, despite the fact that they appeared in Python, starting with version 2.2 • an example of creating convenient and extensible interface classes using descriptors.
The report describes the low-level features of Python code execution. Various trade-offs between speed and security, which are dictated by the architecture of the interpreter, are considered. Also considered are best practices for integration and optimization, which can be useful to users of a language from different areas.
The main points of the report: • advantages of using fabric; • fabfiles as a compilation of the list of commands on a remote server; • ordering work through ssh; • flexibility and ease of use fabric.
In general, as we expected, there was a complete “informality” at the meeting, the speakers felt neither the speakers nor the listeners - in the course of the questions / answers the participants went to the speakers from the hall to offer their own method of solving a specific problem.
The report by Nikita Lesnikov, "A cursory review of the guts of the Python interpreter" caused a storm of emotions and an ardent "continuation of the banquet" in the next meeting. As a result, the second part of Nikita's report was shown in the third mitap, but more on that in the next series :)