Re: [Python-Dev] Current patch process question

2009-07-08 Thread Scott David Daniels
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

Re: [Python-Dev] Current patch process question

2009-07-08 Thread Martin v. Löwis
>> 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

Re: [Python-Dev] Current patch process question

2009-07-08 Thread Antoine Pitrou
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