Daniel Kahn Gillmor writes:
> nmbug and notmuch-report are developer tools. It's 2018, and all
> developers should have python3 available.
>
Pushed.
d
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch
On Thu 2020-03-12 18:57:51 +0200, Tomi Ollila wrote:
> I've been running nmbug with a wrapper that runs python 2.7 (since default
> python in that particular machine is python 2.6 -- which doesn't work with
> nmbug (or it may but that is complicated, i'm not sure...).
>
> So, to me just doing 1,s/
On Thu, Mar 12 2020, Daniel Kahn Gillmor wrote:
> Two years later, I'd like to re-propose this patch that moves nmbug to
> python3.
>
> I have read what PEP 394 says (thanks for the pointer, Trevor!) but in
> practice (a) i do not see debian pointing /usr/bin/python to python3 any
> time in the ne
Two years later, I'd like to re-propose this patch that moves nmbug to
python3.
I have read what PEP 394 says (thanks for the pointer, Trevor!) but in
practice (a) i do not see debian pointing /usr/bin/python to python3 any
time in the near future, (b) python2 is officially EOL, and (c) i don't
ha
On Mon 2018-02-12 09:53:33 -0800, W. Trevor King wrote:
> That Python-2-only tool should be using python2 in its shebang. This
> is exactly the sort of issue that PEP 394 was created to address.
Thanks for the suggestion, i've asked them to do that:
https://bugs.debian.org/890282
> Once you patc
On Thu, Feb 15, 2018 at 07:37:53AM +0200, Tomi Ollila wrote:
> In this case I value Trevor as valid notmuch maintainer as anyone
> else who has done significant work for nmbug.
Thanks, but I don't think that should impact the decision for this
patch. I'm just sharing my take, but the eventual dec
On Mon, Feb 12 2018, W. Trevor King wrote:
> On Sun, Feb 11, 2018 at 10:56:36PM -0500, Daniel Kahn Gillmor wrote:
>> On Fri 2018-02-09 12:46:24 -0800, W. Trevor King wrote:
>> > From later on in PEP 394 [1]:
>> >
>> > It is anticipated that there will eventually come a time where
>> > the thir
On Sun, Feb 11, 2018 at 10:56:36PM -0500, Daniel Kahn Gillmor wrote:
> On Fri 2018-02-09 12:46:24 -0800, W. Trevor King wrote:
> > From later on in PEP 394 [1]:
> >
> > It is anticipated that there will eventually come a time where
> > the third party ecosystem surrounding Python 3 is sufficien
On Fri 2018-02-09 12:46:24 -0800, W. Trevor King wrote:
> From later on in PEP 394 [1]:
>
> It is anticipated that there will eventually come a time where the
> third party ecosystem surrounding Python 3 is sufficiently mature
> for this recommendation to be updated to suggest that the python
On Fri, Feb 09, 2018 at 01:36:48PM -0500, Daniel Kahn Gillmor wrote:
> > Is there something using python3 gets you for nmbug that you miss
> > with python2?
>
> Yep, i get to remove python 2 from my operating system :)
>
> Smaller installed codebase, fewer bugs. There are only two
> outstanding h
On Fri 2018-02-09 09:12:57 -0800, W. Trevor King wrote:
> On Thu, Feb 08, 2018 at 11:32:11PM -0500, Daniel Kahn Gillmor wrote:
>> nmbug and notmuch-report are developer tools. It's 2018, and all
>> developers should have python3 available.
>
> From PEP 394 [1]:
>
> One exception to this is scrip
On Thu, Feb 08, 2018 at 11:32:11PM -0500, Daniel Kahn Gillmor wrote:
> nmbug and notmuch-report are developer tools. It's 2018, and all
> developers should have python3 available.
From PEP 394 [1]:
One exception to this is scripts that are deliberately written to be
source compatible with bo
nmbug and notmuch-report are developer tools. It's 2018, and all
developers should have python3 available.
Signed-off-by: Daniel Kahn Gillmor
---
devel/nmbug/nmbug | 2 +-
devel/nmbug/notmuch-report | 5 ++---
2 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/devel/nmbug/n
13 matches
Mail list logo