From: Michael Haggerty <mhagger@alum.mit.edu>
To: John Keeping <john@keeping.me.uk>
Cc: git@vger.kernel.org
Subject: Re: [RFC/PATCH v2] CodingGuidelines: add Python coding guidelines
Date: Fri, 01 Feb 2013 09:39:39 +0100 [thread overview]
Message-ID: <510B7F4B.7040902@alum.mit.edu> (raw)
In-Reply-To: <20130130203158.GN1342@serenity.lan>
On 01/30/2013 09:31 PM, John Keeping wrote:
> On Wed, Jan 30, 2013 at 11:05:10AM +0100, Michael Haggerty wrote:
>> [...] maybe we should establish a small Python library of
>> compatibility utilities (like a small "six"). [...]
>> But I haven't had time to think of where to put such a library, how to
>> install it, etc.
>
> If we want to go that route, I think restructuring the
> "git_remote_helpers" directory and re-using its infrastructure for
> installing the "Git Python modules" would be the way to go. The
> directory structure would become something like this:
>
> git/
> `-- python/
> |-- Makefile # existing file pulled out of git_remote_helpers
> |-- < some new utility library >
> |-- git_remote_helpers
> | |-- __init__.py
> | |-- git
> | | |-- __init__.py
> | | |-- exporter.py
> | | |-- git.py
> | | |-- importer.py
> | | |-- non_local.py
> | | `-- repo.py
> | `-- util.py
> |-- setup.cfg # existing file pulled out of git_remote_helpers
> `-- setup.py # existing file pulled out of git_remote_helpers
>
>
> It looks like the GitPython project[1] as already taken the "git" module
> name, so perhaps we should use "git_core" if we do introduce a new
> module.
>
> [1] http://pypi.python.org/pypi/GitPython
This sounds reasonable. But not all Python code will go under the
"python" subdirectory, right? For example, I am working on a Python
script that fits thematically under contrib/hooks.
OTOH (I'm thinking aloud here) it is probably a bad idea for a hook
script to depend on a Python module that is part of git itself. Doing
so would make the hook script depend on a particular version of git (or
at least a version with a compatible Python module). But users might be
reluctant to upgrade git just to install a hook script.
Michael
--
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
next prev parent reply other threads:[~2013-02-01 8:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 19:08 [RFC/PATCH v2] CodingGuidelines: add Python coding guidelines John Keeping
2013-01-29 19:34 ` Junio C Hamano
2013-01-29 19:55 ` John Keeping
2013-01-30 10:05 ` Michael Haggerty
2013-01-30 20:31 ` John Keeping
2013-02-01 8:39 ` Michael Haggerty [this message]
2013-02-01 11:16 ` John Keeping
2013-02-03 15:12 ` Pete Wyckoff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=510B7F4B.7040902@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=git@vger.kernel.org \
--cc=john@keeping.me.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).