blob: 8cf65c59179fbfa68b1d166f0ae41893f665c5f4 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
|
<!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=%3CCAPSgDyLPxNotL%3DQPEmtmZQ2j8AuG%2BcA7bmiZguX93sCr3%2BXzxw%40mail.gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="006573.html">
<LINK REL="Next" HREF="006597.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Python Packaging Policy</H1>
<B>philippe makowski</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Python%20Packaging%20Policy&In-Reply-To=%3CCAPSgDyLPxNotL%3DQPEmtmZQ2j8AuG%2BcA7bmiZguX93sCr3%2BXzxw%40mail.gmail.com%3E"
TITLE="[Mageia-dev] Python Packaging Policy">makowski.mageia at gmail.com
</A><BR>
<I>Wed Jul 13 09:51:16 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="006573.html">[Mageia-dev] Python Packaging Policy
</A></li>
<LI>Next message: <A HREF="006597.html">[Mageia-dev] Python Packaging Policy
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6576">[ date ]</a>
<a href="thread.html#6576">[ thread ]</a>
<a href="subject.html#6576">[ subject ]</a>
<a href="author.html#6576">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>2011/7/13 Michael scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>>:
><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>And how do you manage package that support both P2 and P3 ?
(same source)
><i> Regarding a review of all package, that sound like daunting task :/
</I>yes, but do you see another solution ?
we can have a priority list
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="006573.html">[Mageia-dev] Python Packaging Policy
</A></li>
<LI>Next message: <A HREF="006597.html">[Mageia-dev] Python Packaging Policy
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6576">[ date ]</a>
<a href="thread.html#6576">[ thread ]</a>
<a href="subject.html#6576">[ subject ]</a>
<a href="author.html#6576">[ 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>
|