Re: Advice wanted: handling weird vendoring situation

2022-02-07 Thread Julian Gilbey
On Mon, Feb 07, 2022 at 09:27:28PM +, Julian Gilbey wrote: > [...] > > I thought I could address this issue by replacing the vendored copies > of the library modules by symlinks to /usr/lib/python3.X/, but now > I've hit another snag: some of these modules import other modules. > For example:

Re: Bug#1005043: lintian: check that Python version numbers are not 0.0.0

2022-02-07 Thread Julian Gilbey
On Tue, Feb 08, 2022 at 12:26:01AM +, Stefano Rivera wrote: > Hi Julian (2022.02.07_06:26:38_+) > > I'm a little confused by this. Have a look at > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005039 against > > python3-iniconfig. It has a very straightforward debian/rules, using

Re: Bug#1005043: lintian: check that Python version numbers are not 0.0.0

2022-02-07 Thread Stefano Rivera
Hi Julian (2022.02.07_06:26:38_+) > I'm a little confused by this. Have a look at > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005039 against > python3-iniconfig. It has a very straightforward debian/rules, using > pybuild, and its setup.py script has "use_scm_version=True", but it >

Advice wanted: handling weird vendoring situation

2022-02-07 Thread Julian Gilbey
Hi, I'm working towards packaging pydevd (which is a recursive dependency of Spyder via IPython), and it's a somewhat challenging package! I have hit an issue and would appreciate some thoughts on how best to handle it. Background: pydevd is a debugging package which can attach to running