On Oct 5, 9:13 am, Terry Reedy <[EMAIL PROTECTED]> wrote:
> Martin Geisler wrote:
> > Steven D'Aprano <[EMAIL PROTECTED]> writes:
> >>> From reading the PEP-3113 I got the impression that the author
> >>> thought that this feature was unused and didn't matter.
>
> And that there were good alternati
I have been working on making Python a secure interpreter to run when
embedded in terms of resources with an object representation (e.g.,
files but not memory or CPU). To save myself from repeating myself
and missing some details of exactly what I have done I am going to
point to a post to my Pyth
st thing I want happening is people finding mistakes in the code. =) But if
enough people request the source I will take the time to generate a tar.bz2
file of patches against the 2.3.4 source release and put them up somewhere.
Below is the abstract culled directly from the thesis it
[The HTML version of this Summary is available at
http://www.python.org/dev/summary/2005-03-16_2005-03-31.html]
=
Summary Announcements
=
---
My last summary
---
So, after nearly 2.5 years, this is my final python-dev Summary. Ste
[The HTML version of this Summary is available at
http://www.python.org/dev/summary/2005-03-01_2005-03-15.html]
=
Summary Announcements
=
-
Second to last summary for me
-
Just a reminder, after this Su
[The HTML version of this Summary is available at
http://www.python.org/dev/summary/2005-02-15_2005-02-28.html]
=
Summary Announcements
=
Status of the candidates
It looks like all three candidates for taking
[The HTML version of this Summary is available at
http://www.python.org/dev/summary/2005-02-01_2005-02-14.html]
=
Summary Announcements
=
--
Giving myself a gold watch
--
As some of you may have already heard o
[taking python-dev off of the Cc: list]
Scott David Daniels wrote:
Brett C. wrote:
I have decided that I am going to stop doing the python-dev Summaries
> after PyCon; the Summary covering the last half of March 2005 will be
> it for me.
I (as well as most, I'd guess) have enjoyed yo
Steve Holden wrote:
Michele Simionato wrote [on c.l.py]:
Brett Cannon:
[... python-dev summary ... boilerplate change ...]
+1 for this idea. The summary looks much better now :)
Keep the good work going,
Sorry, but i have to disagree. I hope you won't take this reply
personally, Michele, since it'
=
Summary Announcements
=
-
School sure likes to destroy my free time
-
A month late, that much closer to having this hectic quarter being over. Sorry
for being so delinquent wi
This is a summary of traffic on the `python-dev mailing list`_ from January 01,
2005 through January 15, 2005. It is intended to inform the wider Python
community of on-going developments on the list. To comment on anything
mentioned here, just post to `comp.lang.python`_ (or email
python-lis
This is a summary of traffic on the `python-dev mailing list`_ from December
16, 2004 through December 31, 2004. It is intended to inform the wider Python
community of on-going developments on the list. To comment on anything
mentioned here, just post to `comp.lang.python`_ (or email
python-l
This is a summary of traffic on the `python-dev mailing list`_ from December
01, 2004 through December 15, 2004. It is intended to inform the wider Python
community of on-going developments on the list. To comment on anything
mentioned here, just post to `comp.lang.python`_ (or email
python-l
python-dev Summary for 2004-11-16 through 2004-11-30
This is a summary of traffic on the `python-dev mailing list`_ from November
16, 2004 through November 30, 2004. It is intended to inform the wider Python
community of on-going developments
This is a summary of traffic on the `python-dev mailing list`_ from October 16,
2004 through October 31, 2004. It is intended to inform the wider Python
community of on-going developments on the list. To comment on anything
mentioned here, just post to `comp.lang.python`_ (or email
python-lis
python-dev Summary for 2004-11-01 through 2004-11-15
This is a summary of traffic on the `python-dev mailing list`_ from November
01, 2004 through November 15, 2004. It is intended to inform the wider Python
community of on-going developments
Anthony Baxter, our ever-diligent release manager, mentioned this past week
that Python 2.3.5 will most likely come to fruition some time in January (this
is not guaranteed date). This means that in order to have enough time to
proper evaluate new patches and bugs they must be reported **now**!
17 matches
Mail list logo