Re: Extensions: py3 compatibility metadata

2020-05-14 Thread Gregory Szorc
On Wed, May 13, 2020 at 5:18 AM Georges Racinet 
wrote:

> Hi all,
>
> I don't think we have anything for third party extensions to claim their
> compatibility with Mercurial on Python 3.
>
> Would it be a good idea to add new metadata, such as `py3testedwith` or
> `py3minimumhgversion`?
>

I had thought about this a while ago as well and never got around to
submitting patches. I think it would be a good idea to have more source
level annotations for extensions to mark compatibility with Mercurial,
Python, etc versions/environments. One could even imagine a configuration
mode where Mercurial refuses to load extensions unless they have
annotations indicating they are compatible. This would be a "safe" way to
transition from Python 2 to 3.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


Extensions: py3 compatibility metadata

2020-05-13 Thread Georges Racinet
Hi all,

I don't think we have anything for third party extensions to claim their
compatibility with Mercurial on Python 3.

Would it be a good idea to add new metadata, such as `py3testedwith` or
`py3minimumhgversion`?

I personally would find the latter to be enough.

Cheers,

-- 
Georges Racinet
https://octobus.net, https://about.heptapod.host, https://heptapod.net
GPG: BF5456F4DC625443849B6E58EE20CA44EF691D39, sur serveurs publics




signature.asc
Description: OpenPGP digital signature
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel