Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] python: fix interpreter directive for python scripts
Date: Sun, 12 Aug 2012 17:27:26 +0200	[thread overview]
Message-ID: <20120812172726.5111b4ef@skate> (raw)
In-Reply-To: <201208121650.03902.yann.morin.1998@free.fr>

Le Sun, 12 Aug 2012 16:50:03 +0200,
"Yann E. MORIN" <yann.morin.1998@free.fr> a ?crit :

> Or introduce a new package infrastrucutre, like for autotools-based and
> cmake-based packages. For example, we could add a "pysetup" (or whatver)
> infrastructure:
> 
>   $(eval $(pysetup-package))
> 
> Which would automatically call ./setup in the package directory, passing the
> proper arguments, instead of reimplementing that in every python packages?

Right. We start to have more and more Python-based packages, and it
seems like those using the Python setuptools could benefit from having
a common infrastructure.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-08-12 15:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-11  6:10 [Buildroot] [PATCH] python: fix interpreter directive for python scripts Jonathan Liu
2012-08-11 21:05 ` Thomas Petazzoni
2012-08-12  6:57   ` Jonathan Liu
2012-08-12 12:04   ` Jonathan Liu
2012-08-12 13:19     ` Avishay Orpaz
2012-08-12 14:50       ` Yann E. MORIN
2012-08-12 15:27         ` Thomas Petazzoni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-08-11  5:43 Jonathan Liu
2012-08-22  7:17 ` Maxime Ripard

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=20120812172726.5111b4ef@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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