At PyCon, we discussed moving Jython's svn repository to Python's with
Martin von Löwis. I would think that Jython would live in Python's hg
repository in the same way as stackless and distutils. Has the
parallel project strategy been determined? Will they be separate
repositories, separate "for
On Sat, Jun 6, 2009 at 4:07 AM, Daniel Diniz wrote:
> anatoly techtonik wrote:
>>
>> It is impossible to edit roundup keywords and this takes away the
>> flexibility in selecting bugs related to a module/function/test or
>> some other aspect of development. For example, I need to gather all
>> sub
Frank Wierzbicki schrieb:
> At PyCon, we discussed moving Jython's svn repository to Python's with
> Martin von Löwis. I would think that Jython would live in Python's hg
> repository in the same way as stackless and distutils. Has the
> parallel project strategy been determined? Will they be se
On Mon, Jun 8, 2009 at 16:29, Frank Wierzbicki wrote:
> At PyCon, we discussed moving Jython's svn repository to Python's with
> Martin von Löwis. I would think that Jython would live in Python's hg
> repository in the same way as stackless and distutils. Has the
> parallel project strategy been
On Sun, Jun 7, 2009 at 6:21 AM, Terry Reedy wrote:
>
> I have thought that 2.7 was now to come out instead with 3.2 and would
> include backported 3.2 new features. Others expect 2.7 to come out soon
> after 3.1 and to only contain new 3.1 features. So Guido or someone, please
> clarify: is 2.7
anatoly techtonik gmail.com> writes:
>
> Just my 0.02 cents, but struggling with all warts of 2.5 subprocessing
> in Windows I would vote for more time for stabilizating things - not
> adding new features. Long awaited subprocess as replacement for
> os.popen() AFAIK is still incapable to asynchr
On Mon, Jun 8, 2009 at 11:32 AM, Dirkjan Ochtman wrote:
> I'd say migrating to Python's svn doesn't make a whole lot of sense at
> this point, but I'll leave that to Martin (since he has to do the
> work). For the conversion, I can just as well take the Jython repo
> from your current server. I've
Frank Wierzbicki schrieb:
> On Mon, Jun 8, 2009 at 11:32 AM, Dirkjan Ochtman wrote:
>> I'd say migrating to Python's svn doesn't make a whole lot of sense at
>> this point, but I'll leave that to Martin (since he has to do the
>> work). For the conversion, I can just as well take the Jython repo
>>
>> Also, Martin suggested we migrate to Python's svn and then go along
>> for the svn->hg ride. Does that still make sense now that some
>> planning has been done?
>
> I don't think so. It should not matter from which repository the conversion
> is done, especially since there is no shared histo
> For my part I'm fine either way (and I agree that Martin should decide
> based on what is best for him).
See my other message. We need to collect SSH keys, and I don't mind
moving the Jython repository. OTOH, if the Jython repository gets
converted into hg right away, it's certainly (a little)
> Just my 0.02 cents, but struggling with all warts of 2.5 subprocessing
> in Windows I would vote for more time for stabilizating things - not
> adding new features. Long awaited subprocess as replacement for
> os.popen() AFAIK is still incapable to asynchronously communicate with
> spawned proces
On Mon, Jun 8, 2009 at 3:57 PM, "Martin v. Löwis" wrote:
> FWIW, I really think that PEP 385 should really grow a timeline
> pretty soon. Are we going to switch this year, next year, or 2011?
>
+1
-- Alexandre
___
Python-Dev mailing list
Python-Dev@pyth
On Mon, Jun 8, 2009 at 21:57, "Martin v. Löwis" wrote:
> See my other message. We need to collect SSH keys, and I don't mind
> moving the Jython repository. OTOH, if the Jython repository gets
> converted into hg right away, it's certainly (a little) less work.
Yeah, I guess if you move it to a se
Hi all,
I've reported bug http://bugs.python.org/issue5924 some time ago and I
think it's a release blocker -- it seems easy to fix, but I don't have
time to actually submit a patch, so, I'd like to draw attention to it,
especially as a release candidate is already out.
Cheers,
Fabio
___
> I've reported bug http://bugs.python.org/issue5924 some time ago and I
> think it's a release blocker -- it seems easy to fix, but I don't have
> time to actually submit a patch, so, I'd like to draw attention to it,
> especially as a release candidate is already out.
In absence of a patch, it c
15 matches
Mail list logo
