Dear Greg:<br><br><div class="gmail_quote">On Mon, Feb 8, 2010 at 9:59 PM, Greg Ewing <span dir="ltr"><<a href="mailto:greg.ewing@canterbury.ac.nz">greg.ewing@canterbury.ac.nz</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">Andrew McNabb wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi. I was just curious whether there are any current plans for Python 3<br>
support in PyGUI.<br>
</blockquote>
<br></div>
None whatsoever as yet. I'm waiting until the dust settles<br>
on Python 3 before even thinking about it.<br><div class="im"></div></blockquote><div><br>Pardon me, but, Python 3 is fully mature. The reason why "nobody" is using it is because package authors are not supporting it. I have made the decision to drop wxPython. Part of the reason I made that decision is because Robin Dunn has no plans for a Python 3 version (or so he said when I asked the same question there as Andrew just asked here.) I am actively moving everything I can over to Python 3, and am depending on you to have a graphics package ready for me. Pywin32 is done. Yes, it took some effort, but it was do-able, and the build system now handles all the differences for new releases. Don't let me down here. I do not want to be stuck with TK.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Also, I didn't notice anything on the PyGUI page about how to make<br>
contributions to the code. Is there a version control system in place<br>
or a bug tracker for submitting patches to?<br>
</blockquote>
<br></div>
No, there isn't, sorry. But you're welcome to send me code<br>
and I'll consider merging it in.<br></blockquote><div><br>In order for PyGui to be a practical choice for long term production
work, it needs to live on a server where the code can continue to be
developed by others -- just in case you get run over by a truck. The
reason that I am the administrator for adodbapi is because the original
author disappeared without a trace. After many months of non-contact,
sourceforge gave me access to continue the work. I picked up the outstanding patches and applied them. The rest is history.<br>
I recommend sourceforge very highly. You can maintain as much
autonomy as you feel you need, and gradually share responsibility when
you are ready. I have also tried google code and launchpad, there are no flies on them, but I still like sourceforge better.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
-- <br><font color="#888888">
Greg</font></blockquote><div><br>By the way... I have been thinking about making an IronPython version of PyGUI -- after I get done with a better (i.e. genuine <a href="http://ADO.NET">ADO.NET</a>) IronPython version of adodbapi. IPy 2.6 is about halfway to Python 3 (there is no difference between str and unicode.) You could get more help with stuff like this if you were to move to a DVCS.<br>
--<br>Vernon<br><br></div></div>