OK, since no one has really said anything, I am going to assume no one
has issues with importlib in terms of me checking it in or choosing a
name for it (I like importlib more than imp so I will probably stick
with that).
So I will do some file renaming and reorganization, get the code set
up to b
On Fri, Jan 09, 2009, Barry Warsaw wrote:
>
> To that end, I'm happy to say that Benjamin Peterson will be the release
> manager for Python 2.7 and 3.1. I will be mentoring him through the
> process, but it'll be his ball of snake wax. Please join me in helping
> him make the 2.7 and 3.1 relea
Glenn Linderman wrote:
> On approximately 1/9/2009 3:40 PM, came the following characters from
> the keyboard of Terry Reedy:
>> Glenn Linderman wrote:
>>> in 2.6 and before execfile is listed in builtin functions, and is not
>>> marked deprecated, and exec is in the simple statements, and is not
>
On approximately 1/9/2009 3:40 PM, came the following characters from
the keyboard of Terry Reedy:
Glenn Linderman wrote:
in 2.6 and before execfile is listed in builtin functions, and is not
marked deprecated, and exec is in the simple statements, and is not
marked deprecated.
Because they a
Glenn Linderman wrote:
in 2.6 and before execfile is listed in builtin functions, and is not
marked deprecated, and exec is in the simple statements, and is not
marked deprecated.
Because they are not going away in 2.7.
in 3.0 execfile is not listed in builtin functions, exec is. exec is
no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Now that Python 2.6 and 3.0 are in maintenance mode, it's time to
start thinking about Python 2.7 and 3.1. While I've enjoyed my redux
service as your release manager for 2.6 and 3.0, I believe it's time
to get some new blood in here.
To that
in 2.6 and before execfile is listed in builtin functions, and is not
marked deprecated, and exec is in the simple statements, and is not
marked deprecated.
in 3.0 execfile is not listed in builtin functions, exec is. exec is
not listed in simple statements.
I guess this is an intended 3.0
On Fri, Jan 9, 2009 at 09:50, Benjamin Peterson wrote:
> This is just a note that the PEP index (PEP 0) is now automatically
> generated, so you need not bother to update any more.
Thanks for getting this done!
-Brett
___
Python-Dev mailing list
Python
This is just a note that the PEP index (PEP 0) is now automatically
generated, so you need not bother to update any more.
--
Regards,
Benjamin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscri
Glenn Linderman wrote:
> I'm getting an error similar to that in
> http://bugs.python.org/issue3628
> when I try to run python2.6 and cherrypy 3.1.1.
>
> I'm too new to see any connection between the symptom and the cure
> described in the above issue... I'd guess that somehow threads imply
an
> e
ACTIVITY SUMMARY (01/02/09 - 01/09/09)
Python tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue
number. Do NOT respond to this message.
2304 open (+65) / 14418 closed (+24) / 16722 total (+89)
Open issues with patches: 797
Average
On Fri, Jan 9, 2009 at 1:48 AM, Giovanni Bajo wrote:
> On Sun, 04 Jan 2009 18:50:09 +0900, Stephen J. Turnbull wrote:
>
>> "Martin v. Löwis" writes:
>>
>> > If "switching to a modern DVCS" means that users now need to start
>> > compiling their VCS before they can check out Python,
>>
>> It does
On Thu, Jan 8, 2009 at 9:07 PM, "Martin v. Löwis" wrote:
>> i'd just ... much rather be completely independent of proprietary
>> software when it comes to building free software.
>
> I guess my question is then: why do you want to use Windows in the
> first place?
ha ha :) the same question wa
On Sun, 04 Jan 2009 18:50:09 +0900, Stephen J. Turnbull wrote:
> "Martin v. Löwis" writes:
>
> > If "switching to a modern DVCS" means that users now need to start
> > compiling their VCS before they can check out Python,
>
> It doesn't mean that. All of the DVCS contenders have Windows and M
Hello,
On Fri, Jan 9, 2009 at 09:07, Glenn Linderman wrote:
> I'm getting an error similar to that in http://bugs.python.org/issue3628
> when I try to run python2.6 and cherrypy 3.1.1.
Please use the issue tracker for this.
For help with python, you should ask on the comp.lang.python newsgroup.
On Fri, Jan 9, 2009 at 9:24 AM, Robert Schwebel
wrote:
>
> Yup, will do.
>
> I suspect that some of the design decisions need discussions; should
> that also take place in the issue tracker, or here on the mailing list?
For the distutils part, you can use the distutils mailing list if you wish,
Hi Antoine,
[sorry for the double post, the mails didn't show up in the archive and
my procmail had missing slash at the end of the rule...]
> Thanks for those patches, but please post them to the issue tracker instead
> (http://bugs.python.org/). If each patch is for a distinct purpose, then ope
I'm getting an error similar to that in http://bugs.python.org/issue3628
when I try to run python2.6 and cherrypy 3.1.1.
I'm too new to see any connection between the symptom and the cure
described in the above issue... I'd guess that somehow threads imply an
extra parameter?
It also seems th
18 matches
Mail list logo
