Python setup.cfg wrongly applied to all python package dependencies

Bug #1761097 reported by Daan W. on 2018-04-04
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Sergio Schvezov

Bug Description

This is just a report of the problem discussed in [1] which I think is still present (or something similar).

The problem is that for rapid-photo-downloader, the cwd during build holds a setup.cfg, which then gets applied to all python installs during build.

I created a (stupid?) adaptation of the author's defunct snapcraft.yaml from [2] which I put at [3].

On a clean digital-ocean applet (Ubuntu 17.10 server) a "snapcraft" call (both with current HEAD and with current "snap install snapcraft --classic" results in an error while installing the first python package, in this case pip:


Related branches

Daan W. (dwynen) wrote :
description: updated
Changed in snapcraft:
assignee: nobody → Sergio Schvezov (sergiusens)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers