emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "François Pinard" <pinard@iro.umontreal.ca>
To: emacs-orgmode@gnu.org
Subject: Re: Seeking advice for conditional code
Date: Thu, 31 Jan 2013 21:25:58 -0500	[thread overview]
Message-ID: <86a9rou5vt.fsf@iro.umontreal.ca> (raw)
In-Reply-To: <86d2wl3qsj.fsf@somewhere.org> (Sebastien Vauban's message of "Thu, 31 Jan 2013 23:56:28 +0100")

"Sebastien Vauban"

> For curiosity, why aren't you considering tangling?

Quick half of a reply, I'll revise the rest of your message later.

That would be far too much of a change for the habits of the team, or at
least, this is how I perceive the equilibrium between developers.
Moreover, some of us are not even Emacs users.

When writing a program, the feeling still has to be that we write a
program, rather than a document describing the program, and from which
the program could be extracted.  Python is rather descriptive as a
language, and while comments are useful, they might be less needed than
in other languages.  This is debatable, of course :-).

The documentation is meant for users, and it was strongly suggested that
we try to keep the documentation within the program as much as possible,
as a way to ease keeping the documentation and the program in good
sync.  Some of us really enjoy Org mode, and this is how came the idea
of this compromise of writing Python doc-strings using Org.

François

  reply	other threads:[~2013-02-01  2:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31 17:09 Seeking advice for conditional code François Pinard
2013-01-31 18:55 ` John Kitchin
2013-01-31 21:03 ` Sebastien Vauban
2013-01-31 22:09   ` François Pinard
2013-01-31 22:56     ` Sebastien Vauban
2013-02-01  2:25       ` François Pinard [this message]
2013-02-01  8:24         ` Sebastien Vauban
2013-02-02  0:46           ` Eric S Fraga

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.orgmode.org/

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

  git send-email \
    --in-reply-to=86a9rou5vt.fsf@iro.umontreal.ca \
    --to=pinard@iro.umontreal.ca \
    --cc=emacs-orgmode@gnu.org \
    /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/org-mode.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).