Control: tags -1 help
Control: forwarded -1 Aidan Delaney
Hi,
I admit I have no idea what might have caused these pkg_resources
related errors and how to fix these.
Any help would be welcome
Andreas.
On Sun, Sep 27, 2020 at 08:45:17PM +0200, Lucas Nussbaum wrote:
> Source: gubbins
>
python/gubbins/common.py::parse_and_run() constructs an absolute path for
the executable and then passes it to pkg_resources.get_distribution(). I
have no idea what does this code want to achieve, as get_distribution()
takes requirement specifications, not file paths.
--
WBR, wRAR
Thank you very much, Andrey.
El dom., 4 oct. 2020 a las 17:42, Andrey Rahmatullin ()
escribió:
> On Sun, Oct 04, 2020 at 05:28:57PM +0200, Fioddor Superconcentrado wrote:
> > I've packaged a project provided via https://pipi.org and I wanted to
> > create a debian/watch file but pipi.org
As I said I'm very new to this and all (python) packages I'm using lately
use the usual python tools (pipy, setup.py, etc) and my first approach has
been to stick as close as possible to the upstream procedures. But I might
very likely be taking a wrong decision. What are the reasons to go for git
Thank you as well, Geert.
And yes. It has taken me some time to come back to this issue but I've
tested and seems to work fine.
El dom., 4 oct. 2020 a las 17:44, Geert Stappers ()
escribió:
> On Sun, Oct 04, 2020 at 05:28:57PM +0200, Fioddor Superconcentrado wrote:
> > I've packaged a project
On Fri, Oct 30, 2020 at 03:18:58PM +0100, Fioddor Superconcentrado wrote:
> As I said I'm very new to this and all (python) packages I'm using lately
> use the usual python tools (pipy, setup.py, etc) and my first approach has
> been to stick as close as possible to the upstream procedures. But I
Control: tags -1 upstream
Control: forewarded -1 https://github.com/sanger-pathogens/gubbins/issues/286
On Fri, Oct 30, 2020 at 02:38:03PM +0500, Andrey Rahmatullin wrote:
> python/gubbins/common.py::parse_and_run() constructs an absolute path for
> the executable and then passes it to
On Fri, Oct 30, 2020 at 2:19 PM Fioddor Superconcentrado wrote:
> As I said I'm very new to this and all (python) packages I'm using lately use
> the usual python tools (pipy, setup.py, etc) and my first approach has been
> to stick as close as possible to the upstream procedures. But I might
On 2020-10-31 01:33:36 + (+), Paul Wise wrote:
> On Fri, Oct 30, 2020 at 2:19 PM Fioddor Superconcentrado wrote:
> > As I said I'm very new to this and all (python) packages I'm
> > using lately use the usual python tools (pipy, setup.py, etc)
> > and my first approach has been to stick as
On Sat, Oct 31, 2020 at 2:31 AM Jeremy Stanley wrote:
> I have to agree, though in the upstream projects with which I'm
> involved, those generated files are basically a lossy re-encoding of
> metadata from the Git repositories themselves: AUTHORS file
> generated from committer headers,
10 matches
Mail list logo
