blob: e3e325cfd7aaec7e0b6b70af64bcbdbf359cf5ac (
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
|
<!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=64d92a8d-e3eb-40f4-986e-c2d37ca30a83%40email.android.com">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="000350.html">
<LINK REL="Next" HREF="000354.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=64d92a8d-e3eb-40f4-986e-c2d37ca30a83%40email.android.com"
TITLE="[pycrypto] Once again: Python3 with PyCrypto">sbehrens at gmx.li
</A><BR>
<I>Wed Dec 29 12:19:28 CST 2010</I>
<P><UL>
<LI>Previous message: <A HREF="000350.html">[pycrypto] Once again: Python3 with PyCrypto
</A></li>
<LI>Next message: <A HREF="000354.html">[pycrypto] Once again: Python3 with PyCrypto
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#353">[ date ]</a>
<a href="thread.html#353">[ thread ]</a>
<a href="subject.html#353">[ subject ]</a>
<a href="author.html#353">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On 12/29/2010 10:44 AM, Dwayne C. Litzenberger wrote:
><i> If you're making lots of changes, it's probably easiest if you fork <A HREF="https://github.com/dlitz/pycrypto">https://github.com/dlitz/pycrypto</A> and push your changes to the master and py3k branches there.
</I>I can do that as an interim step. I have no desire to actually fork
pycrypto, though. I'd like to see these changes land on trunk, for a
pycrypto that can build and run on 2.1 through 2.7 as well as 3.1/3.2.
Do I hear you right that you'd like to see a forked repository so you
can check it out and be comfortable with it, and then merge the changes
back into your master repository?
Thorsten
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="000350.html">[pycrypto] Once again: Python3 with PyCrypto
</A></li>
<LI>Next message: <A HREF="000354.html">[pycrypto] Once again: Python3 with PyCrypto
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#353">[ date ]</a>
<a href="thread.html#353">[ thread ]</a>
<a href="subject.html#353">[ subject ]</a>
<a href="author.html#353">[ 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>
|
