I hope posting job vacancies does not violate established list
netiquette. The job in question is mainly to do with the PyPy EU project.
-- Alastair
---
Alastair Burt
German Centre for AI (DFKI), Stuhlsatzenhausweg 3
Saarbruecken 66123, Germany
Email: [EMAIL PROTECTED]
Tel: +49 681 302 2565
On Friday 04 February 2005 09:04, [EMAIL PROTECTED] wrote:
> I hope posting job vacancies does not violate established list
> netiquette. The job in question is mainly to do with the PyPy EU project.
There's a Python Job Board on python.org; see
http://www.python.org/Jobs-howto.html
for in
Alastair> I hope posting job vacancies does not violate established list
Alistair> netiquette. The job in question is mainly to do with the PyPy
Alistair> EU project.
Not a huge faux pas, but you will get much better exposure by submitting it
to the Python Job Board. Details on posti
[EMAIL PROTECTED]
> Log Message:
> Add NEWS item about future parser bug.
Give back the time machine!
--
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/list
On Fri, 4 Feb 2005 10:46:52 -0800, Guido van Rossum
<[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED]
> > Log Message:
> > Add NEWS item about future parser bug.
>
> Give back the time machine!
I already will have by the time you needed it.
Jeremy
___
Pyt
On 4-feb-05, at 20:00, Jeremy Hylton wrote:
Add NEWS item about future parser bug.
Give back the time machine!
I already will have by the time you needed it.
I knew this was going to happen one day.
(And now we should all be getting out our copies of the HHGTTG and work
out the horrible future pas
Anyone like to commit 1028908?
Patch was written by module author (me), including an important doc
warning re (lack of) thread safety which I mistakenly thought had got into
2.4.0.
John
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.pyth
On Thu, 3 Feb 2005, Guido van Rossum wrote:
[...]
> hope at least one person from the release team can be involved, e.g.
[...]
Guido, from python-announce list:
[...]
> Python 2.3.5 will be released from www.python.org within a few days
> containing a fix for this issue. Python 2.4.1 will be rele
Ok, so here's the state of play: 2.3.5 is currently aimed for next Tuesday,
but there's an outstanding issue - the new copy code appears to have
broken something, see www.python.org/sf/1114776 for the gory details.
I'm completely out of time this weekend to look into it too closely - if
someone ha
On Saturday 05 February 2005 05:38, [EMAIL PROTECTED] wrote:
> Fix bug that allowed future statements virtually anywhere in a module.
>
> If we exit via the break here, we need to set ff_last_lineno or
> FUTURE_POSSIBLE() will remain true. The bug affected statements
> containing a variety of expr
[Anthony]
> While this is undoubtedly a bug fix, I'm not sure that it should be
> backported - it will break people's code that is "working" now (albeit
> in a faulty way). What do people think?
I concur -- the balance of risks is towards the patch causing more harm
than good.
Raymond
_
11 matches
Mail list logo
