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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [pycrypto] Once again: Python3 with PyCrypto
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:pycrypto%40lists.dlitz.net?Subject=%5Bpycrypto%5D%20Once%20again%3A%20Python3%20with%20PyCrypto&In-Reply-To=">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="000304.html">
<LINK REL="Next" HREF="000307.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[pycrypto] Once again: Python3 with PyCrypto</H1>
<B>Thorsten Behrens</B>
<A HREF="mailto:pycrypto%40lists.dlitz.net?Subject=%5Bpycrypto%5D%20Once%20again%3A%20Python3%20with%20PyCrypto&In-Reply-To="
TITLE="[pycrypto] Once again: Python3 with PyCrypto">sbehrens at gmx.li
</A><BR>
<I>Wed Dec 22 20:11:19 CST 2010</I>
<P><UL>
<LI>Previous message: <A HREF="000304.html">[pycrypto] Help on PyCrypto errors on 64-bit Windows
</A></li>
<LI>Next message: <A HREF="000307.html">[pycrypto] Once again: Python3 with PyCrypto
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#305">[ date ]</a>
<a href="thread.html#305">[ thread ]</a>
<a href="subject.html#305">[ subject ]</a>
<a href="author.html#305">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Johannes, Dwayne,
now that pycrypto accepts US contributions, I'm happy to at least give Python 3.x support some thought and investigation. So as to not re-invent the wheel: Johannes, what's the status of your efforts to date?
>><i>
</I>I don't really know what's involved in doing Py3k support, but I'd like to see it happen, provided
that it doesn't involve breaking Python 2.x support or a lot of unnecessary code duplication.
>><i>
</I>
Agreed. It's a matter of staying away from 3.x-only features (a pretty good list can be found here: <A HREF="http://sayspy.blogspot.com/2010/08/what-will-forever-be-exclusive-to.html">http://sayspy.blogspot.com/2010/08/what-will-forever-be-exclusive-to.html</A>), and I'd say even features that have been backported into 2.6 and 2.7. That is, focus on rewriting things that will break 3.x in such a way that they stay supported in 2.x. I'll caution that I haven't been through that exercise. I imagine it should be non-trivial but also not a huge pain for pycrypto, but I'm not willing to wager on that hunch.
The biggest hurdle has already been overcome: You'd like to see it happen. That's not a given in the Python community right now, I am made to understand. :)
>><i>
</I>How do other Python projects that have C code maintain compatibility across both Python 2.x and 3.x?
>><i>
</I>
There are some guidelines at <A HREF="http://docs.python.org/release/3.0.1/howto/cporting.html#cporting-howto.">http://docs.python.org/release/3.0.1/howto/cporting.html#cporting-howto.</A> Looks like the int/long unification can be handled pretty well, by using aliases. str/unicode may be an issue, since 2.6 has a compatibility header, but earlier versions don't. Depends on how much those functions are in use in the pycrypto C modules. And then there's module unit/status, which looks like a pain, though do-able.
Yours
Thorsten
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="000304.html">[pycrypto] Help on PyCrypto errors on 64-bit Windows
</A></li>
<LI>Next message: <A HREF="000307.html">[pycrypto] Once again: Python3 with PyCrypto
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#305">[ date ]</a>
<a href="thread.html#305">[ thread ]</a>
<a href="subject.html#305">[ subject ]</a>
<a href="author.html#305">[ author ]</a>
</LI>
</UL>
<hr>
<a href="http://lists.dlitz.net/cgi-bin/mailman/listinfo/pycrypto">More information about the pycrypto
mailing list</a><br>
</body></html>
|
