summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-July/006573.html
blob: 6701f4d60ac6856cbf470da93bff20faed8a3924 (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
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
<!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=%3C20110713071306.GA23669%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="006554.html">
   <LINK REL="Next"  HREF="006576.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=%3C20110713071306.GA23669%40sisay.ephaone.org%3E"
       TITLE="[Mageia-dev] Python Packaging Policy">misc at zarb.org
       </A><BR>
    <I>Wed Jul 13 09:13:06 CEST 2011</I>
    <P><UL>
        <LI>Previous message: <A HREF="006554.html">[Mageia-dev] Python Packaging Policy
</A></li>
        <LI>Next message: <A HREF="006576.html">[Mageia-dev] Python Packaging Policy
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#6573">[ date ]</a>
              <a href="thread.html#6573">[ thread ]</a>
              <a href="subject.html#6573">[ subject ]</a>
              <a href="author.html#6573">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>On Tue, Jul 12, 2011 at 03:03:46PM +0200, philippe makowski wrote:
&gt;<i> Hi,
</I>&gt;<i> 
</I>&gt;<i> remember this first draft (<A HREF="http://mageia.org/wiki/doku.php?id=python_policy">http://mageia.org/wiki/doku.php?id=python_policy</A>)
</I>&gt;<i> that is still a draft
</I>&gt;<i> 
</I>&gt;<i> now we have also Python3 so we really need to write our policy
</I>&gt;<i> I see mainly two majors points :
</I>&gt;<i> 
</I>&gt;<i> 1/ pyc, pyo management
</I>&gt;<i> 2/ having Python2 and Python3
</I>&gt;<i> 
</I>&gt;<i> about 1/ :
</I>&gt;<i> it seems that the best would be to package only py (smallest packages)
</I>&gt;<i> and having triggers on install and on remove to manage pyc and pyo
</I>&gt;<i> (That's in fact the Debian way
</I>&gt;<i> (<A HREF="http://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html#s-byte_compilation">http://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html#s-byte_compilation</A>))
</I>&gt;<i> 
</I>&gt;<i> if we go this way, we need someone to write triggers and people to
</I>&gt;<i> review all Python packages
</I>&gt;<i> (I'm ok to work on that review, for triggers, I have no clue on how to
</I>&gt;<i> do, but may be that with some help I could try)
</I>
The tricky part was not to make sure that file are properly ghosted ?
 
&gt;<i> about 2/ :
</I>&gt;<i> 
</I>&gt;<i> again we have to review all Python packages to see if they run under
</I>&gt;<i> Python3 or not and to package them for Python2 and Python3
</I>&gt;<i> (I'm ok to work on that review)
</I>&gt;<i> may be that the Fedora policy can help us for that ?:
</I>&gt;<i> <A HREF="http://fedoraproject.org/wiki/Packaging/Python">http://fedoraproject.org/wiki/Packaging/Python</A>
</I>
I would be in favor of treating python2 and python 3 as 2 differents languages.
The rational is that :
- we cannot garantee to have support for both
-  we will likely have some module who would be updated only on 
python 3 sooner or later
- we will need to do upgrade of package at different time, since both python2 and python3 are
released at different time.

So rather than a complex scheme that will confuse packagers, just consider they 
are separate, and use the almost same policy ( with s/python/python3/ )

Regarding a review of all package, that sound like daunting task :/
-- 
Michael Scherer
</PRE>
























































<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="006554.html">[Mageia-dev] Python Packaging Policy
</A></li>
	<LI>Next message: <A HREF="006576.html">[Mageia-dev] Python Packaging Policy
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#6573">[ date ]</a>
              <a href="thread.html#6573">[ thread ]</a>
              <a href="subject.html#6573">[ subject ]</a>
              <a href="author.html#6573">[ 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>