Using it you can say that installing lxml requires libxml on the target machine. Combining the two views: dh-virtualenvĭebian packaging has one significant advantage over plain Python packaging: It has the ability to define dependencies on system libraries. This is also what developers are accustomed to and the slap in the face is pretty harsh when they see our systems for the first time. This all is then installed into a dedicated virtualenv, that makes sure system libraries won’t affect your code. If you look at practically any existing Python project in the outside world, they basically follow the same pattern: setup.py or requirements.txt defines all the installation requirements, and all of them are available for installation from the Python Package Index, PyPI. And Debian packaging has a somewhat steep learning curve. In order to push out the software the dev has been working on she needs to know how to package Python inside Debian packages in first place. Second, bigger problem, is that when you hire a proficient Python developer, you can safely assume the developer knows how to use Python packaging. This leads to the need of backporting newer packages into our internal debian repositories. Given that we run the Debian stable, the packages, even at the time of the release of the stable version, are often outdated and missing features. There are, however, some drawbacks on the developer side.įirst drawback is the state of the Debian Python packages. For deploying software this system works fairly well when augmented with puppet. To build them, we have our continuous integration platform with sbuild building and uploading them automatically from each commit. At Spotify, we have deployed Python software in Debian packages for a fairly long time.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |