Py3 - Script to eliminate compatibility warnings.

Martijn Pieters mj at zopatista.com
Tue Feb 23 05:17:19 EST 2016


On 21 February 2016 at 22:06, Pulkit Goyal <7895pulkit at gmail.com> wrote:
> Since I am new to community and still understanding how it works, I don't
> know how to send patches. So i will be needing a bit of help on it for
> future. Moreover I want to take part in GSOC-16 and work with everyone out
> there. Any sort of guidelines are welcomed.

Start with the https://www.mercurial-scm.org/wiki/DeveloperInfo
information; it tells you how to contribute code, like what standards
we require.

However, know that simply putting in the `from __future__ import
absolute_import` line at the top may well *not* be enough, or the
entirely the wrong thing to do for third-party code imported into the
mercurial repository. If it was this simple, we'd already have done
it!

The mailing list is mirrored in various places that let you search;
perhaps you could look through what others have done in this area?
http://markmail.org/search/?q=list%3Amercurial-devel+subject%3Aabsolute_import#query:list%3Amercurial-devel%20subject%3Aabsolute_import
searches the markmail.org archive for any email talking about
absolute_import specifically.

-- 
Martijn Pieters


More information about the Mercurial-devel mailing list