summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20110119/002228.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/20110119/002228.html')
-rw-r--r--zarb-ml/mageia-dev/20110119/002228.html104
1 files changed, 104 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110119/002228.html b/zarb-ml/mageia-dev/20110119/002228.html
new file mode 100644
index 000000000..b961f4ea3
--- /dev/null
+++ b/zarb-ml/mageia-dev/20110119/002228.html
@@ -0,0 +1,104 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Python Packaging Policy
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Python%20Packaging%20Policy&In-Reply-To=%3C20110118235540.GE20740%40sisay.ephaone.org%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="002227.html">
+ <LINK REL="Next" HREF="002231.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Python Packaging Policy</H1>
+ <B>Michael scherer</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Python%20Packaging%20Policy&In-Reply-To=%3C20110118235540.GE20740%40sisay.ephaone.org%3E"
+ TITLE="[Mageia-dev] Python Packaging Policy">misc at zarb.org
+ </A><BR>
+ <I>Wed Jan 19 00:55:40 CET 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="002227.html">[Mageia-dev] Proofreading web applications policy
+</A></li>
+ <LI>Next message: <A HREF="002231.html">[Mageia-dev] Python Packaging Policy
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#2228">[ date ]</a>
+ <a href="thread.html#2228">[ thread ]</a>
+ <a href="subject.html#2228">[ subject ]</a>
+ <a href="author.html#2228">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>On Tue, Jan 18, 2011 at 08:51:26PM +0100, Antoine Pitrou wrote:
+&gt;<i> On Mon, 17 Jan 2011 09:21:56 +0100
+</I>&gt;<i> Michael scherer &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>&gt; wrote:
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; There is also the issue on bytecompilation ( <A HREF="https://qa.mandriva.com/show_bug.cgi?id=50484">https://qa.mandriva.com/show_bug.cgi?id=50484</A> ).
+</I>&gt;<i> &gt; I have exposed there the various problem, and apart from explaining
+</I>&gt;<i> &gt; that the solution I chosed was not better than the other, no one gave a compeling
+</I>&gt;<i> &gt; argument into one or the others alternatives.
+</I>&gt;<i>
+</I>&gt;<i> That depends how &quot;compelling&quot; you expect the argument to be :)
+</I>&gt;<i> The current situation is clearly not satisfactory.
+</I>
+I agree that the solution is not perfect for everybody, and if
+I had one that would not be without problem, I would have adopted it.
+
+&gt;<i> The solution of generating bytecode at install time looks fine. I am
+</I>&gt;<i> not an RPM specialist though, but if you have non-RPM specific questions
+</I>&gt;<i> feel free to ask them, I'd be glad to answer.
+</I>
+Well, that's not satisfying from a rpm pov, unfortunately.
+But with some patchs, that the one that I would use, yes.
+until that, i prefer know documented breakage, than new undocumented breakage.
+(ie, shadok proverb, if you want to have less unhappy people, just hit always the
+same ).
+
+&gt;<i> &gt; Finally, a vast part of the policy is handling 2to3, a topic that we didn't discuss
+</I>&gt;<i> &gt; at all, and I would not be confortable to adopt it without first looking at it and
+</I>&gt;<i> &gt; discussing it.
+</I>&gt;<i>
+</I>&gt;<i> What is the issue with &quot;handling 2to3&quot;? It's a developer tool and
+</I>&gt;<i> certainly shouldn't be invoked at install time if that's what you are
+</I>&gt;<i> asking. Generally, I don't think you (as a packager) have to invoke
+</I>&gt;<i> 2to3 manually at all. If 2to3 is part of the packaged software's build
+</I>&gt;<i> process, then their setup.py will probably invoke it automatically with
+</I>&gt;<i> the right options.
+</I>
+I as more speaking of the transition from pyton 2 to python 3. I think the easiest
+on a policy point of view is to handle this like 2 separate languages, but that mean twice the work.
+And so we should at least try to do better ( not sure that we can, of course ).
+--
+Michael Scherer
+
+&gt;<i> Regards
+</I>&gt;<i>
+</I>&gt;<i> Antoine.
+</I>&gt;<i>
+</I>&gt;<i>
+</I></PRE>
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="002227.html">[Mageia-dev] Proofreading web applications policy
+</A></li>
+ <LI>Next message: <A HREF="002231.html">[Mageia-dev] Python Packaging Policy
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#2228">[ date ]</a>
+ <a href="thread.html#2228">[ thread ]</a>
+ <a href="subject.html#2228">[ subject ]</a>
+ <a href="author.html#2228">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
+mailing list</a><br>
+</body></html>