Stop spaming our server. Please remove all the email addresses containing
@kelseus.com domain
from your mailing list.
Sanket Patel
Network Engineer
Kelseus Ltd
DDI: +44 (0)1223 471235
Fax: +44 (0)1223 471220
http://www.kelseus.com
-----Original Message-----
From: python-dev-request at python.org
[mailto:python-dev-request at python.org]
Sent: Tuesday, August 05, 2003 5:01 PM
To: python-dev at python.org
Subject: Python-Dev Digest, Vol 1, Issue 3435
Send Python-Dev mailing list submissions to
python-dev at python.org
To subscribe or unsubscribe via the World Wide Web, visit
http://mail.python.org/mailman/listinfo/python-dev
or, via email, send a message with subject or body 'help' to
python-dev-request at python.org
You can reach the person managing the list at
python-dev-owner at python.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Python-Dev digest..."
Today's Topics:
1. Re: python-dev Summary for 2003-07-01 through 2003-07-31
[draft] (Michal Wallace)
2. Re: python-dev Summary for 2003-07-01 through 2003-07-31
[draft] (Brett C.)
3. New place for python-mode bug reports and patches (Skip Montanaro)
4. RE: Re: Re: pirate (python+parrot) (logistix)
5. Re: Re: pirate (python+parrot) (Michael Hudson)
6. Re: Python 2.3 maintenance branch is now open (Jack Jansen)
7. RE: python-dev Summary for 2003-07-01 through 2003-07-31
[draft] (Michael Chermside)
8. Re: Python 2.3 maintenance branch is now open (Michael Hudson)
9. Re: Python 2.3 maintenance branch is now open (Barry Warsaw)
10. IDLE NEWS and Version (Kurt B. Kaiser)
----------------------------------------------------------------------
Message: 1
Date: Mon, 4 Aug 2003 23:20:43 -0400 (EDT)
From: Michal Wallace <michal at sabren.com>
Subject: Re: [Python-Dev] python-dev Summary for 2003-07-01 through
2003-07-31 [draft]
To: brett at python.org
Cc: python-dev at python.org
Message-ID:
<Pine.LNX.4.44.0308042315540.31222-100000 at hydrogen.sabren.com>
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Mon, 4 Aug 2003, Brett C. wrote:
> Another offer sprung up this month from Michal Wallace to host our
> CVS at http://www.versionhost.com/ with the hitch that the server
> would be pserver only which would thus most likely only work for
> anonymous checkouts
Not at all! That's the whole point. :)
And if you like using ssh, there's always stunnel, or:
http://www.sabren.net/code/cvssh/
Sincerely,
Michal J Wallace
Sabren Enterprises, Inc.
-------------------------------------
contact: michal at sabren.com
hosting: http://www.cornerhost.com/
my site: http://www.withoutane.com/
--------------------------------------
------------------------------
Message: 2
Date: Mon, 04 Aug 2003 20:25:08 -0700
From: "Brett C." <bac at OCF.Berkeley.EDU>
Subject: Re: [Python-Dev] python-dev Summary for 2003-07-01 through
2003-07-31 [draft]
To: Michal Wallace <michal at sabren.com>
Cc: brett at python.org, python-dev at python.org
Message-ID: <3F2F2394.4070807 at ocf.berkeley.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Michal Wallace wrote:
> On Mon, 4 Aug 2003, Brett C. wrote:
>
>
>>Another offer sprung up this month from Michal Wallace to host our
>>CVS at http://www.versionhost.com/ with the hitch that the server
>>would be pserver only which would thus most likely only work for
>>anonymous checkouts
>
>
> Not at all! That's the whole point. :)
>
> And if you like using ssh, there's always stunnel, or:
> http://www.sabren.net/code/cvssh/
>
Glad to hear that! I know I would not be the only one who would
strongly object to moving the CVS over to anything that didn't have some
form of SSH protection (and allowed for SSH keys since I know I am too
damn lazy to type my password in constantly =) .
-Brett
------------------------------
Message: 3
Date: Mon, 4 Aug 2003 22:49:02 -0500
From: Skip Montanaro <skip at pobox.com>
Subject: [Python-Dev] New place for python-mode bug reports and
patches
To: python-list at python.org, python-dev at python.org,
python-mode at python.org
Message-ID: <16175.10542.302239.792809 at montanaro.dyndns.org>
Content-Type: text/plain; charset=us-ascii
As many of you are already aware, Barry Warsaw recently created a new
project on SourceForge to house the python-mode.el code which makes Emacs
and XEmacs so delightful to edit Python code. I just completed migrating
all open bugs and patches which mention python-mode from the python project
to the new python-mode project. In the future, please submit all bugs and
patches at
http://sourceforge.net/projects/python-mode/
All new bugs and patches regarding python-mode should be submitted to the
new project.
There's also a mailing list, python-mode at python.org, to which you can
subscribe in the usual Pythonic fashion:
http://mail.python.org/mailman/listinfo/python-mode
Skip
------------------------------
Message: 4
Date: Tue, 5 Aug 2003 02:58:32 -0400
From: "logistix" <logistix at cathoderaymission.net>
Subject: RE: [Python-Dev] Re: Re: pirate (python+parrot)
To: "'A.M. Kuchling'" <amk at amk.ca>, <python-dev at python.org>
Message-ID: <000001c35b1e$fc938a60$20bba8c0 at XP>
Content-Type: text/plain; charset="us-ascii"
[guido at python.net]
> wrote:
> > Sure, but bytecode evolves slowly enough to be useful for Dan; given
> > that the only parse tree format we have is *intricately* linked with
> > the Python parser and (at least part of) its runtime,
>
[AMK]
> It is? Both translators are using the compiler package, not
> the parser
> module; can it be said to be intricately linked with the runtime?
> Admittedly it uses the parser module underneath, but the AST
> representation
> itself is pretty generic, isn't it?
>
As Michal touched on earlier, I wrote a hand-coded pure-python parser
that plugs into the compiler package. It takes about 1.5-2x as long to
compile vs using the native parser module. The resultant tuples can
also be shoved back into genuine parse trees via parser.sequence2ast().
So yeah, it's not that big of a deal to generate AST trees without the
runtime (until some crazy function attribute syntax gets added to
python, that is)
http://www.cathoderaymission.net/~logistix/python/pparser.py
-Grant
------------------------------
Message: 5
Date: Tue, 05 Aug 2003 11:22:09 +0100
From: Michael Hudson <mwh at python.net>
Subject: Re: [Python-Dev] Re: pirate (python+parrot)
To: python-dev at python.org
Message-ID: <2mllu8qu9a.fsf at starship.python.net>
Content-Type: text/plain; charset=us-ascii
Guido van Rossum <guido at python.net> writes:
> Interesting indeed. The focus on bytecode is understandable: let
> someone else write a parser, so Parrot won't have to. But from
> skimming his log, Dan seems to take the bytecode too seriously;
> it's really only meant to be a quick way for the parser to output
> something. In particular, bytecode hacks were never a goal.
Really? You surprise me <wink>.
Cheers,
mwh
--
3. Syntactic sugar causes cancer of the semicolon.
-- Alan Perlis, http://www.cs.yale.edu/homes/perlis-alan/quotes.html
------------------------------
Message: 6
Date: Tue, 5 Aug 2003 12:47:47 +0200
From: Jack Jansen <Jack.Jansen at cwi.nl>
Subject: Re: [Python-Dev] Python 2.3 maintenance branch is now open
To: Barry Warsaw <barry at python.org>
Cc: LIST Python Developers <python-dev at python.org>
Message-ID: <4053FFDF-C732-11D7-BB10-0030655234CE at cwi.nl>
Content-Type: text/plain; charset=US-ASCII; format=flowed
On Tuesday, Aug 5, 2003, at 00:58 Europe/Amsterdam, Barry Warsaw wrote:
> Jack turned over the release23-branch branch to me so I was able to
> create the Python 2.3 maintenance branch. Here's what I did:
>
> - checked out release23-fork
> - cvs tag -b release23-maint
> - cvs up -rrelease23-maint
> - cvs up -j release23-branch
> - cvs commit
Barrt,
how about porting things back to the trunk? Is that my responsibility
for the stuff I changed between 2.3 and 2.3-mac?
--
Jack Jansen, <Jack.Jansen at cwi.nl>, http://www.cwi.nl/~jack
If I can't dance I don't want to be part of your revolution -- Emma
Goldman
------------------------------
Message: 7
Date: Tue, 5 Aug 2003 04:30:28 -0700
From: Michael Chermside <mcherm at mcherm.com>
Subject: [Python-Dev] RE: python-dev Summary for 2003-07-01 through
2003-07-31 [draft]
To: python-dev at python.org
Message-ID: <1060083028.3f2f95543a9a2 at mcherm.com>
Content-Type: text/plain; charset=ISO-8859-1
Brett writes:
> I would appreciate not just correctional feedback but just overall
> feedback as well for this summary. I have changed the format once again
> as well as the general philosophy behind the Summaries
Brett, you're doing great as usual. Saving enough time to survive
grad school may have been your primary motivation, but I actually
think that this revised format is better than your exhaustive one.
IMHO people who wanted to know every detail that went on would just
subscribe to python-dev, and people who wanted historical accuracy
would just consult the list archives. Your summaries made these
tasks easier, but could never be as exhaustive as just reading the
list. However, the "more journalistic" approach is really nice
because it helps to separate out the relevent from the insignifigant.
It is a very useful filtering of the information, providing
something you CAN'T get by reading the list. Of course, it's *your*
idea of what's important and what's not, but at this point I'd say
you're as qualified as any to make that call, and more qualified
than almost all.
Keep up the great work!
-- Michael Chermside
------------------------------
Message: 8
Date: Tue, 05 Aug 2003 12:31:08 +0100
From: Michael Hudson <mwh at python.net>
Subject: Re: [Python-Dev] Python 2.3 maintenance branch is now open
To: python-dev at python.org
Message-ID: <2m8yq8qr2b.fsf at starship.python.net>
Content-Type: text/plain; charset=us-ascii
Barry Warsaw <barry at python.org> writes:
> Jack turned over the release23-branch branch to me so I was able to
> create the Python 2.3 maintenance branch. Here's what I did:
>
> - checked out release23-fork
> - cvs tag -b release23-maint
> - cvs up -rrelease23-maint
> - cvs up -j release23-branch
> - cvs commit
>
> IOW, I basically branched release23-maint off of the release23-fork tag
> on the trunk, then I merged all the changes in the release23-branch to
> the release23-maint.
Here's a recipe I use for branches that others might find useful:
$ cd ~/src/python/dist/
$ cvs co -d src-23x -r release23-maint python/dist/src
(This creates -- eventually -- a src-23x directory alongside the src
directory which contains the trunk)
Then hack CVS/Entries to contain a line
D/src-23x////
Now running cvs up in python/dist/ will update both the trunk and the
release23-maint code (and in my case release22-maint, too).
Cheers,
mwh
--
Just point your web browser at http://www.python.org/search/ and
look for "program", "doesn't", "work", or "my". Whenever you find
someone else whose program didn't work, don't do what they
did. Repeat as needed. -- Tim Peters, on python-help, 16 Jun 1998
------------------------------
Message: 9
Date: 05 Aug 2003 08:44:58 -0400
From: Barry Warsaw <barry at python.org>
Subject: Re: [Python-Dev] Python 2.3 maintenance branch is now open
To: Jack Jansen <Jack.Jansen at cwi.nl>
Cc: LIST Python Developers <python-dev at python.org>
Message-ID: <1060087498.8108.2.camel at anthem>
Content-Type: text/plain
On Tue, 2003-08-05 at 06:47, Jack Jansen wrote:
> Barrt,
> how about porting things back to the trunk? Is that my responsibility
> for the stuff I changed between 2.3 and 2.3-mac?
I wasn't planning on porting things back to the trunk, so it would be
great if you could do it.
-Barry
------------------------------
Message: 10
Date: Tue, 05 Aug 2003 11:54:50 -0400
From: kbk at shore.net (Kurt B. Kaiser)
Subject: [Python-Dev] IDLE NEWS and Version
To: python-dev at python.org
Message-ID: <m3znionlpx.fsf at float.attbi.com>
Content-Type: text/plain; charset=us-ascii
IDLE has historically maintained its own NEWS file, and it is now
accessible from IDLE's Help/About menu. Maintaining this file has the
advantage that all the IDLE NEWS is kept in one place and is easily
parsable for display.
Do we want to continue this tradition or merge IDLE NEWS into Python
NEWS on a go-forward basis?
Second, do we want to continue the IDLE versioning (currently 1.0)
or just drop it now that IDLE is no longer distributed separately?
--
KBK
------------------------------
_______________________________________________
Python-Dev mailing list
Python-Dev at python.org
http://mail.python.org/mailman/listinfo/python-dev
End of Python-Dev Digest, Vol 1, Issue 3435
*******************************************
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4