diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-July/006597.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-July/006597.html | 136 |
1 files changed, 136 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-July/006597.html b/zarb-ml/mageia-dev/2011-July/006597.html new file mode 100644 index 000000000..d10574a85 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-July/006597.html @@ -0,0 +1,136 @@ +<!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=%3C4E1D6F52.8030707%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="006576.html"> + <LINK REL="Next" HREF="006698.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Python Packaging Policy</H1> + <B>andre999</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Python%20Packaging%20Policy&In-Reply-To=%3C4E1D6F52.8030707%40laposte.net%3E" + TITLE="[Mageia-dev] Python Packaging Policy">andr55 at laposte.net + </A><BR> + <I>Wed Jul 13 12:11:30 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="006576.html">[Mageia-dev] Python Packaging Policy +</A></li> + <LI>Next message: <A HREF="006698.html">[Mageia-dev] Python Packaging Policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6597">[ date ]</a> + <a href="thread.html#6597">[ thread ]</a> + <a href="subject.html#6597">[ subject ]</a> + <a href="author.html#6597">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>philippe makowski a écrit : +><i> 2011/7/13 Michael scherer<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>>: +</I>>><i> +</I>>><i> I would be in favor of treating python2 and python 3 as 2 differents languages. +</I>>><i> The rational is that : +</I>>><i> - we cannot garantee to have support for both +</I>>><i> - we will likely have some module who would be updated only on +</I>>><i> python 3 sooner or later +</I>>><i> - we will need to do upgrade of package at different time, since both python2 and python3 are +</I>>><i> released at different time. +</I>>><i> +</I>>><i> So rather than a complex scheme that will confuse packagers, just consider they +</I>>><i> are separate, and use the almost same policy ( with s/python/python3/ ) +</I>><i> And how do you manage package that support both P2 and P3 ? +</I>><i> (same source) +</I> +If we use misc's approach, we could minimize the urgency of the conversion. +If upstream supports both, we could either add a virtual provides in P2 and P3 +for that (to be used only by such packages), or support just P3 (or maybe just P2). +I don't know which is best, but I'd still like to help out. + +>><i> Regarding a review of all package, that sound like daunting task :/ +</I>><i> yes, but do you see another solution ? +</I>><i> we can have a priority list +</I> +-- +André +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="006576.html">[Mageia-dev] Python Packaging Policy +</A></li> + <LI>Next message: <A HREF="006698.html">[Mageia-dev] Python Packaging Policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6597">[ date ]</a> + <a href="thread.html#6597">[ thread ]</a> + <a href="subject.html#6597">[ subject ]</a> + <a href="author.html#6597">[ 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> |