On 5/9/20 1:03 PM, Gary Mills wrote:
On Sat, May 09, 2020 at 03:03:57PM +, Andy Fiddaman wrote:
On Sat, 9 May 2020, Gary Mills wrote:
; That's the change that caused the problem. The first line becomes
; only a comment when the file is interpreted by python. Removing that
; option string
On Sat, May 09, 2020 at 03:03:57PM +, Andy Fiddaman wrote:
> On Sat, 9 May 2020, Gary Mills wrote:
>
> ; That's the change that caused the problem. The first line becomes
> ; only a comment when the file is interpreted by python. Removing that
> ; option string would solve the problem in a
On Sat, 9 May 2020, Gary Mills wrote:
; That's the change that caused the problem. The first line becomes
; only a comment when the file is interpreted by python. Removing that
; option string would solve the problem in a simpler way. I wonder why
; it was ever put there? I see that it was
On Sat, May 09, 2020 at 06:48:34AM +, Alexander Pyhalov wrote:
>Likely by default it passed -Es to the python interpreter, so doesn't
>load modules from non-standart path.
Ah, I didn't notice that the first line of /usr/bin/pkglint is now:
#!/usr/bin/python3.5 -Es
The previous
Likely by default it passed -Es to the python interpreter, so doesn't load
modules from non-standart path.
С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ
От:
