Martin v. Löwis wrote:
There seem to be two places to plausibly introduce a change: py3k and
trunk. Should I submit changes for trunk, py3k, or both?
Patches are usually first checked into trunk, and then svnmerge'd to py3k.
So it makes more sense to submit your patch against trunk.
For
>> There seem to be two places to plausibly introduce a change: py3k and
>> trunk. Should I submit changes for trunk, py3k, or both? I tried
>> asking in the initial feature request, but nobody replied, and I finally
>> decided that I'd go for patching trunk in the interim.
>
> Patches are usual
Hi,
> There seem to be two places to plausibly introduce a change: py3k and
> trunk. Should I submit changes for trunk, py3k, or both? I tried
> asking in the initial feature request, but nobody replied, and I finally
> decided that I'd go for patching trunk in the interim.
Patches are usually
I am confused by the current hydra-like development. I've recently
submitted a change (issue6422 -- a feature request) which is currently
moving through the process. I am not particularly asking for special
attention on that issue, but I am confused about the process I should be
using (in the fa
