Good morning!
Could you help me to get `pip freeze` and `pip list` to display only
packages installed by pip and to exclude packages coming from a Debian
package?
The only way I've found is
import pip
for dist in pip.get_installed_distributions():
if dist.location.startswith('/usr/loc
On Friday 05 September 2014 12:32:12 Szépe Viktor wrote:
> Could you help me to get `pip freeze` and `pip list` to display only
> packages installed by pip and to exclude packages coming from a Debian
> package?
Have you already tried using --local option?
$ mkvirtualenv --system-site-package
On Friday 05 September 2014 12:47:28 you wrote:
> $ mkvirtualenv --system-site-packages
Ehm...
$ mkvirtualenv --system-site-packages testlocal
Cheers,
--
Daniele Tricoli 'Eriol'
http://mornie.org
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscr
Thank you!
I am not a python developer but a sysadmin.
I would use pip in a monthly report on a VPS.
https://github.com/szepeviktor/debian-server-tools/blob/master/monitoring/package-versions.sh#L86
So it is about system-wide python packages from
- pip
- and Debian packages.
Idézem/Quoting Da
On 04/09/14 20:40, Barry Warsaw wrote:
> The file is patched, but now I have an d/p/0005- file instead of a modified
> 0003- patch file. Sigh.
The systemd maintainers configured git-buildpackage (in their
debian/gbp.conf) to not use patch numbers. I'm starting to think that's
The Right Thing in g
On 05/09/14 13:10, Simon McVittie wrote:
> On 04/09/14 20:40, Barry Warsaw wrote:
>> The file is patched, but now I have an d/p/0005- file instead of a modified
>> 0003- patch file. Sigh.
>
> The systemd maintainers [...]
It might also be worth noting that the systemd maintainers switched from
g
On Sep 05, 2014, at 01:10 PM, Simon McVittie wrote:
>The systemd maintainers configured git-buildpackage (in their
>debian/gbp.conf) to not use patch numbers. I'm starting to think that's
>The Right Thing in general.
Agreed. I've filed wishlist bug #760578 for this, and other enhancements to
pat
On Sep 05, 2014, at 01:21 PM, Simon McVittie wrote:
>It might also be worth noting that the systemd maintainers switched from
>git-dpm to gbp-pq recently (between 204 and 208, I think), so they
>obviously didn't think git-dpm was the better option.
Are there any artifacts of this switch, e.g. mai
On 05/09/14 15:53, Barry Warsaw wrote:
> On Sep 05, 2014, at 01:21 PM, Simon McVittie wrote:
>
>> It might also be worth noting that the systemd maintainers switched from
>> git-dpm to gbp-pq recently (between 204 and 208, I think), so they
>> obviously didn't think git-dpm was the better option.
Hi,
It took me a long time to figure out what was going on, but now I think
I get it. Let me explain my issue.
In OpenStack, there's lots of modules sharing the same "oslo" namespace.
Here's the list of what's currently in Debian:
- python-oslo.config
- python-oslo.messaging
- python-oslo.rootwr
Hey all,
Simon McVittie [2014-09-05 16:05 +0100]:
> >> It might also be worth noting that the systemd maintainers switched from
> >> git-dpm to gbp-pq recently (between 204 and 208, I think), so they
> >> obviously didn't think git-dpm was the better option.
I don't think anyone in pkg-systemd@ h
On Fri, Sep 05, 2014 at 11:16:53PM +0800, Thomas Goirand wrote:
> But in Python 3.4, there's no such a file. While this doesn't seem to be
> a problem with the packages once installed, it is breaking unit tests.
> For example, building python-oslo.serialization and running the unit
> tests, I get:
On 05/09/14 16:18, Martin Pitt wrote:
> I don't think anyone in pkg-systemd@ has looked at git-dpm yet. In
> fact we switched from gitpkg to standard git-buildpackage.
Ugh, sorry.
> So I'm not sure where "switched from git-dpm" came from?
"smcv mis-remembering the situation", evidently.
S
Hi Martin, thanks for the information.
On Sep 05, 2014, at 05:18 PM, Martin Pitt wrote:
>gitpkg is rather complicated to use and set up, only about 3 people in
>Debian know how it works properly, and it makes it really hard to
>track a set of changes against trunk over time (i. e. the equivalent
Quick follow up. Since yesterday, I filed a few bugs on the git-dpm package
and already got back some useful information.
* tag format
This is configurable, so it's easy to get the gbp style tags. These commands
set the style in the repo so I think it should be propagated to anybody who
checks
On Sep 05, 2014, at 11:28 AM, Paul Tagliamonte wrote:
>Empty init is totally valid - http://legacy.python.org/dev/peps/pep-0420/
Right, but just to be clear, as you noted the presence of *any* __init__.py
regardless of contents, makes it a "regular" (i.e. concrete) package instead
of a namespace
On Sep 05, 2014, at 11:16 PM, Thomas Goirand wrote:
>Surprisingly, when I just do (as root):
>
>echo "" >/usr/lib/python3/dist-packages/oslo/__init__.py
>
>then everything works again, and subunit under Python3.4 can find the
>local version of oslo.serialization.
Is there by any chance a /usr/lib
17 matches
Mail list logo