From: "Petteri Räty" <betelgeuse@gentoo.org>
To: Arfrever Frehtes Taifersar Arahesis <Arfrever@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [gentoo-dev-announce] Changes in python_mod_optimize(), python_mod_cleanup() and python_mod_compile()
Date: Tue, 25 May 2010 22:11:44 +0300 [thread overview]
Message-ID: <4BFC20F0.2080107@gentoo.org> (raw)
In-Reply-To: <201005252036.08716.Arfrever@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
On 05/25/2010 09:35 PM, Arfrever Frehtes Taifersar Arahesis wrote:
> - Not passing of paths to python_mod_optimize() and python_mod_cleanup() has been
> deprecated and will be disallowed on 2010-09-01. You should pass paths to Python
> modules to these functions.
>
> - python_mod_compile() has been deprecated and will be banned on 2010-09-01.
> You should use python_mod_optimize() instead of python_mod_compile().
>
1. Messages to gentoo-dev-announce should also be posted to an on topic
mailing lists
2. What does disallowed and banned mean in this case? Plenty of ebuilds
currently pass paths to python_mod_optimize. If you break the stable
tree, you should have the wrath of more people than me. It can be done
at the dates you say if the tree is in order by then.
Regards,
Petteri
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]
next parent reply other threads:[~2010-05-25 19:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201005252036.08716.Arfrever@gentoo.org>
2010-05-25 19:11 ` Petteri Räty [this message]
2010-05-25 20:49 ` [gentoo-dev] Re: [gentoo-dev-announce] Changes in python_mod_optimize(), python_mod_cleanup() and python_mod_compile() Arfrever Frehtes Taifersar Arahesis
2010-05-26 3:14 ` Nirbheek Chauhan
2010-05-26 5:28 ` Alec Warner
2010-05-26 5:47 ` Petteri Räty
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=4BFC20F0.2080107@gentoo.org \
--to=betelgeuse@gentoo.org \
--cc=Arfrever@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox