Message227160
| Author |
gvanrossum |
| Recipients |
chatgris, gvanrossum, vstinner, yselivanov |
| Date |
2014年09月20日.16:32:38 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CAP7+vJJ12UTuJ2=NZO1GOAKis9621Nd_wL8Uj2eYYKyAtK_q5w@mail.gmail.com> |
| In-reply-to |
<1411228962.0.0.62806004254.issue22448@psf.upfronthosting.co.za> |
| Content |
We can merge the changes into 3.4 and 3.5 for you, it's just a simple copy
(the codebases are identical). However, the 3.4.2 release candidate is
apparently in 2 days, so I think you've missed that train already.
On Sat, Sep 20, 2014 at 9:02 AM, Joshua Moore-Oliva <report@bugs.python.org>
wrote:
>
> Joshua Moore-Oliva added the comment:
>
> > You can contribute upstream to the Tulip project first.
>
> Will I be writing a patch and tests for tulip, and then separate a patch
> and tests for python 3.4? Or will I submit to tulip, and then the changes
> will get merged from tulip into python by some other process?
>
> If possible, I would like to get this into python 3.4.2 (assuming all goes
> well).
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue22448>
> _______________________________________
> |
|