Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

On Thu, Jun 16, 2016 at 3:29 AM, Donald Stufft wrote: > Now you install a new version of setuptools that breaks the OS installed > gyp and suddenly now you can’t build your static files anymore. ​gyp or node-gyp don't depend on python-setuptools, at least not on Ubuntu. Are you referring to som

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

On Wed, Jun 15, 2016 at 5:10 PM, Ionel Cristian Mărieș wrote: > > On Thu, Jun 16, 2016 at 2:57 AM, Donald Stufft wrote: >> >> Of course It still applies to Docker. You still have an operating system >> inside that container and unless you install zero Python using packages from >> the system then

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

> On Jun 15, 2016, at 8:10 PM, Ionel Cristian Mărieș wrote: > > ​You're correct, theoretically. But in reality is best to not stick a dozen > services or apps in a single docker image. It’s not really about services as it is about things that you might need *for the service*. For instance, ma

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

On Thu, Jun 16, 2016 at 2:57 AM, Donald Stufft wrote: > Of course It still applies to Docker. You still have an operating system > inside that container and unless you install zero Python using packages > from the system then all of that can still conflict with your own > application’s dependenci

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

> On Jun 15, 2016, at 7:54 PM, Ionel Cristian Mărieș via Distutils-SIG > wrote: > > A sound argument. However, none of that applies to a Docker image. You'd have > a single set of dependencies, so what's the point of using unnecessary tools > and abstractions. :-)​ Of course It still applie

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

On Thu, Jun 16, 2016 at 1:52 AM, Reinout van Rees wrote: > Aaargh, that Gliph talk gave me a *lot* of food for thought. And that's a > good thing. > ​His main argument is that not using a virtualenv can lead to version conflicts. Eg: app you installed with apt will probably break if it depends o

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

On Wed, Jun 15, 2016 at 3:52 PM, Reinout van Rees wrote: [...] > It is a very valid point that seems to point solidly at wheels. As, if you > use a virtualenv, you don't have access to system python packages. And > that's one of the main reasons why the company I work for (still) uses > buildout.

[Distutils] Notice: PyPI APIs now return 403 when accessed via HTTP

In part of an ongoing effort to improve the security of PyPI, instead of redirecting (or silently allowing) requests made over HTTP to PyPI APIs, these APIs will now return a 403 and require people to make the initial request over HTTPS. This does not affect the UI portions of the site that are

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

Op 15-06-16 om 19:38 schreef Nathaniel Smith: For a lot of good general information on these subjects, I recommend Glyph's talk at pycon this year: https://www.youtube.com/watch?v=5BqAeN-F9Qs That's the most valuable youtube video I saw this year! One point that's discussed is why you defin

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

Op 15-06-16 om 13:53 schreef Jim Fulton: 1. Creating production docker images works best when all you're doing is installing a bunch of binary artifacts (e.g. .debs, eggs, wheels). That's where pip and its "everything is in requirements.txt anyway" has an advantage. The buildouts I use alway

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

Op 15-06-16 om 11:31 schreef Ionel Cristian Mărieș via Distutils-SIG: ... I wrote some ideas about that here if you have patience (it's a bit too long read). I definitively have the patience for such a long r

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

On Wed, Jun 15, 2016 at 2:07 AM, Reinout van Rees wrote: > Situation: I'm experimenting with docker, mostly in combination with > buildout. But it also applies to pip/virtualenv. > ... > Now local development: it is normal to mount the current directory as > /code/, so that now is overlayed over t

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

For a lot of good general information on these subjects, I recommend Glyph's talk at pycon this year: https://www.youtube.com/watch?v=5BqAeN-F9Qs One point that's discussed is why you definitely should use virtualenv inside your containers :-) -n On Jun 15, 2016 2:07 AM, "Reinout van Rees" wro

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

On Wed, Jun 15, 2016 at 7:57 AM, Donald Stufft wrote: > >> On Jun 15, 2016, at 7:53 AM, Jim Fulton wrote: >> >> If you actually build programs as part of image building, then your >> image contains build tools, leading to image bloat and potentially >> security problems as the development tools p

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

> On Jun 15, 2016, at 7:53 AM, Jim Fulton wrote: > > If you actually build programs as part of image building, then your > image contains build tools, leading to image bloat and potentially > security problems as the development tools provide a greater attack > surface. This isn’t strictly true

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

On Wed, Jun 15, 2016 at 5:07 AM, Reinout van Rees wrote: > Hi, > > Buzzword bingo in the subject... > > Situation: I'm experimenting with docker, mostly in combination with > buildout. But it also applies to pip/virtualenv. > > I build a docker container with a Dockerfile: install some .deb packag

Re: [Distutils] Docker, development, buildout, virtualenv, local/global install

On Wed, Jun 15, 2016 at 12:07 PM, Reinout van Rees wrote: > Now local development: it is normal to mount the current directory as > /code/, so that now is overlayed over the originally-added-to-the-docker > /code/. > > This means that anything done inside /code/ is effectively discarded in > deve

[Distutils] Removal of wheels deleting more than the data files

I discovered a quite serious bug in wheels ( http://bugs.python.org/issue27317) When specifying an empty list for the list of data_files in a given directory, the entire directory is being deleted on uninstall of the wheel, even if it contained other resources from other pacakges. Example: from

[Distutils] Docker, development, buildout, virtualenv, local/global install

Hi, Buzzword bingo in the subject... Situation: I'm experimenting with docker, mostly in combination with buildout. But it also applies to pip/virtualenv. I build a docker container with a Dockerfile: install some .deb packages, add the current directory as /code/, run buildout (or pip), re