unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Fabian Ezequiel Gallina <galli.87@gmail.com>
To: Christoph <cschol2112@googlemail.com>
Cc: Chong Yidong <cyd@stupidchicken.com>,
	monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: A new major-mode for Python
Date: Thu, 17 Feb 2011 15:22:42 -0300	[thread overview]
Message-ID: <AANLkTimG6HZMC81Qt_eOxAw4nSrYrH_jZheMo6NA5LgH@mail.gmail.com> (raw)
In-Reply-To: <4D5C9CF9.6020002@gmail.com>

2011/2/17 Christoph <cschol2112@googlemail.com>:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>> I'm not so much concerned about backward compatibility, really.  I just
>> would rather have a smoother transition.
>
> I think the move can be done step by step and shouldn't take too long
> overall.
>
>> I'm not too concerned about features.  I just want the transition to be
>> done in meaningful chunks.  E.g. one commit can rip out the old
>> indentation and install your new one.  Another one could be "drop
>> bycicle because noone wants to repair the repairman".

Sounds reasonable to me. Let's do it.

>
> [...]
>
>> I think we can work something out.  And if Christoph is OK with helping
>> along, this could go very smoothly.
>
> I am OK with that.
>
> Here is what I would propose for the next steps:
>
> If Fabian is OK with the general approach described by you and Chong and
> OK with signing the FSF papers, he should go ahead and do that. In the
> meantime, we could polish Fabians implementation as hosted on github and
> start thinking about the integration in steps.

I do agree, and I sent the form request already, they should get back
to me soon.

>
> By polish, I mean a) resolve issues the current implementation has (I have
> been using it for a couple of days and found a couple, especially on
> Windows) and b) implement the features that are in the Emacs' python.el but
> not in Fabians implementation and that we don't want to loose.
>
> I am available in whatever capacity Fabian is comfortable, i.e. as a
> tester/bug reporter or I can provide patches for improvements.
>

Any help is appreciated, I assume you have signed the papers already
so any contribution will be OK to inclusion.

> As for the integration with the current python.el, I think that some
> cleanup is needed first. For example the pdbtrack implementation that
> was done a couple of years ago pulled in all this unecessary code that
> was never cleaned up. I would clean up this part right away. Then maybe
> remove bicycle repair main support and other stuff that we decide is not
> really required. I think, this will make integrating Fabians changes
> easier.
>
> Fabian, what do you think?
>

That sounds nice. If you could start those cleanups in the current
python.el part the merge should get even simpler.


Regards,
-- 
Fabián E. Gallina
http://www.from-the-cloud.com



  reply	other threads:[~2011-02-17 18:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-17  3:58 A new major-mode for Python Christoph
2011-02-17 18:22 ` Fabian Ezequiel Gallina [this message]
2011-02-18  0:31   ` Christoph
2011-03-28 22:55     ` Fabian Ezequiel Gallina
2011-03-28 23:21       ` Christoph Scholtes
  -- strict thread matches above, loose matches on Subject: below --
2011-02-15  8:05 Fabian Ezequiel Gallina
2011-02-15 22:52 ` Stefan Monnier
2011-02-16  1:44   ` Chong Yidong
2011-02-16  6:46   ` Fabian Ezequiel Gallina
2011-02-16 15:20     ` Stefan Monnier
2011-02-16 15:34     ` Chong Yidong
2011-02-16 14:23 ` Neal Becker
2011-02-17 18:12   ` Fabian Ezequiel Gallina
2011-02-17  4:04 ` m h
2011-02-17 18:36   ` Fabian Ezequiel Gallina

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTimG6HZMC81Qt_eOxAw4nSrYrH_jZheMo6NA5LgH@mail.gmail.com \
    --to=galli.87@gmail.com \
    --cc=cschol2112@googlemail.com \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).