After some discussion in IRC on this topic there was an idea just to write and push upstream needed tools using objgraph w/o having it in the requirements.txt at all. We just need to make sure that those tools are never used during production runs and unit tests (CI will help to verify that). If needed, objgraph can be manually installed used when we need to investigate something.
If such practice is considered OK and doesn’t violate any OpenStack guidelines then I think this would work, at least in my case. Thanks Renat Akhmerov @Nokia On 29 Mar 2018, 15:00 +0700, Renat Akhmerov <renat.akhme...@gmail.com>, wrote: > Hi, > > Can we consider to add objgraph [1] to OpenStack global requirements? I found > this library extremely useful for investigating memory leaks in Python > programs but unfortunately I can’t push upstream any code using it. It seems > to be pretty mature and supports all needed Python versions. > > Or maybe there’s some alternative already available in the OpenStack > requirements? > > [1] https://pypi.python.org/pypi/objgraph/3.4.0 > > > Thanks > > Renat Akhmerov > @Nokia
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
