Mailing List Archive: RFC: python2 (only) script status

RFC: python2 (only) script status

Aug 4, 2021, 8:13 PM

Post #1 of 3 (475 views)

When updating my build scripts by adding
python bytecompiling for those files typically
in /usr/share/mythtv... I found a number of
files that are still python2 only and generate
syntax errors when attempting to bytecompile
(clearly they will not run in distros that are
python3 only, which is becoming the norm).

While the files in question are not of interest
to me personally, so I am unlikely to try to
evaluate any needed changes, is there any
interest in me opening github issues for these
files just so that the (future) work needed is
explicitly tracked (rather than possibly implicitly
known to a few). And if so, should it be one
issue for all the files, or one issue per "group"
(in some cases a number of files are
associated with each other), or one issue per
file?

Thanks for any guidance you can provide.
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

Re: RFC: python2 (only) script status [ In reply to ]

pb.mythtv at gmail

Aug 5, 2021, 6:28 AM

Post #2 of 3 (475 views)

Permalink

On 8/4/21 11:13 PM, Gary Buhrmaster wrote:
> When updating my build scripts by adding
> python bytecompiling for those files typically
> in /usr/share/mythtv... I found a number of
> files that are still python2 only and generate
> syntax errors when attempting to bytecompile
> (clearly they will not run in distros that are
> python3 only, which is becoming the norm).
>
> While the files in question are not of interest
> to me personally, so I am unlikely to try to
> evaluate any needed changes, is there any
> interest in me opening github issues for these
> files just so that the (future) work needed is
> explicitly tracked (rather than possibly implicitly
> known to a few). And if so, should it be one
> issue for all the files, or one issue per "group"
> (in some cases a number of files are
> associated with each other), or one issue per
> file?
>
> Thanks for any guidance you can provide.
> _______________________________________________

Hi Gary

I would say one issue for all of the files would be best.

Does 2to3 work for the files? I used it to convert one python file and
it did a fine job. Maybe somebody can just run that against the list of
files that need converting.

Peter

_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

Re: RFC: python2 (only) script status [ In reply to ]

gary.buhrmaster at gmail

Aug 5, 2021, 8:45 PM

Post #3 of 3 (474 views)

Permalink

On Thu, Aug 5, 2021 at 1:29 PM Peter Bennett <pb.mythtv@gmail.com> wrote:

> I would say one issue for all of the files would be best.

Thanks, I'll add it to my todo list.

> Does 2to3 work for the files?

In some cases it does, but in some cases
the scripts themselves need to be updated
due to upstream changes, so the correct
fix (with actual testing) requires more work
than simply hiding any syntax errors.
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org