M.-A. Lemburg wrote:
> AFAIK, this is a first in the Python repository. Not
> sure if it's such a good idea. Branching and tagging
> doesn't work with external resources in Subversion,
> so things can become inconsistent.
>
> Also, what if you break the code in the berlios repo
> or the server is
Martin v. Löwis wrote:
> > My initial thought was that we could ask alpha testers to run this script on
> > their alpha builds, and report back, but it just struck me that the
> > "buildbot"
> > already builds stuff on a couple of interesting platforms.
> >
> > Can buildbot deal with custom test/
Tim Peters wrote:
> Yes. please. svn:externals should always pin to a specific revision
> (or at least to a "frozen" tag). Updating to a new revision then is
> just a propedit away (to change the revision number); ditto for
> backing off to an older revision if the newer one has problems.
wasn'
Scott David Daniels wrote:
> OK I carried the code I offered earlier in this whole thread (tweaked in
> reaction to some comments) over to comp.lang.python, gathered some
> feedback, and put up a recipe on the cookbook. After a week or so for
> more comment, I'll be happy to submit a patch to inc
Tony Meyer wrote:
> Fredrik Lundh kicked off a surprisingly long thread when he proposed
> that typing "quit" or "exit" in the interactive prompt actually exit
> (i.e. raises SystemError)
SystemExit
> >>> def exit():
> ... print &
Alex Martelli wrote:
> > As you already suspected, I think a PEP is needed. The intent of
>
> I'll be happy to write it, if it stands any chance.
>
> > basestring was to *only* be used as the base class for *built-in*
> > string types. Clearly what you're proposing is different (Decimal is
> > not
Bob Ippolito wrote:
> I want binary all the time when I'm dealing with bitflags and such.
> Of course, I'm trained to be able to read bits in hex format, but it
> would be nicer to see the flags as-is. Even worse when you have to
> deal with some kind of file format where fields are N bits long,
[EMAIL PROTECTED] wrote:
>Skip> A shortcoming in int() hardly seems like a good reason to mess
>Skip> with str().
>
>Gareth> How's it a shortcoming in int() that it doesn't do anything
>Gareth> with, say, int(2.345,19)?
>
> My reasoning was that just because int() was written to ig
Guido van Rossum wrote:
> I think we ought to let this sit for a while and come back to it in a
> few week's time. Is 'base' really the right name? It could just as
> well be considered a conversion in the other direction.
the same applies to hex and oct, of course.
as for base itself, I'm more
Guido wrote:
> > What Fredrik hacks together there (http://www.effbot.org/lib) is very
> > impressive. I especially like the "permalinks" in this style:
> >
> > http://effbot.org/lib/os.path.join
>
> Which (despite having "perma" in its name) evaporates and leaves
> behind a link to os.path.html#j
Georg Brandl wrote:
> > Vertical spacing is IMHO pretty bad on this page. Everything
> > has the same distance from everything else. This makes under-
> > standing the structure of the page pretty hard.
>
> The main content is the original zipfile.html from
> http://www.effbot.org/lib/zipfile.html
> (this is the main motivator behind my documentation and site efforts; we
should learn not to press control-enter when we mean enter.
anyway, what I intended to say was that we should work harder on lowering the
threshold for drive-by contributions; it should be possible for anyone to
notice a
Guido van Rossum wrote:
> > On this page, 8 of 30 entries have a 'new in' comment. For anyone with no
> > interest in the past, these constitute noise. I wonder if for 3.0, the
> > timer can be reset and the docs start clean again. To keep them backwards
> > compatible, they would also have to
Guido wrote:
> Have you studied wikipedia's approach? It's multi-layered and worth
> learning from (start with their FAQ on editing).
>
> (And by the way, I am *not* advocating writing the docs as one big
> wikipedia -- only the user commentary.)
to clarify, I'm advocating maintaining the docs vi
BJörn Lindqvist wrote:
> > > Have you studied wikipedia's approach? It's multi-layered and worth
> > > learning from (start with their FAQ on editing).
> > >
> > > (And by the way, I am *not* advocating writing the docs as one big
> > > wikipedia -- only the user commentary.)
> >
> > to clarify, I
Neal Norwitz wrote:
> > > > Does that make sense? We would just need /f's script in SVN.
> > >
> > > in python/Tools/something or sandbox/something ?
> >
> > python/Doc/tools/something?
>
> Fredrik were you still working on that? I can make the changes to the
> bb master. I thought Trent's sugg
Brett Cannon wrote:
> And to /F, kudos from me. I have been randomly thinking about it and
> I understand your desire for semantic markup now.
thanks.
> Hopefully something can get hammered out so that at least the Python
> 3 docs can premiere having been developed on by the whole community.
w
I wrote:
> Neal Norwitz wrote:
>
> > > > > Does that make sense? We would just need /f's script in SVN.
> > > >
> > > > in python/Tools/something or sandbox/something ?
> > >
> > > python/Doc/tools/something?
> >
> > Fredrik were you still working on that? I can make the changes to the
> > bb ma
Gustavo J. A. M. Carneiro wrote:
> > # Operations on path strings.
> > def abspath(sef): ...
> > def normcase(self): ...
> > def normpath(self): ...
> > def realpath(self): ...
> > def expanduser(self): ...
> > def expandvars(self): ...
> >
Gustavo J. A. M. Carneiro wrote:
> > If a URI class implemented the same methods, it would be something of a
> > question whether uri.joinpath('/foo/bar', 'baz') would return '/foo/baz'
> > (and urlparse.urljoin would) or '/foo/bar/baz' (as os.path.join does).
> > I assume it would be be the latte
BJörn Lindqvist wrote:
> However, I might be wrong because according to [1] it should work. And
> having to wrap the Path object in str() (open(str(somepath))) each and
> every time the called function expects a string is not a practical
> solution.
in Python, the usual way to access an attribute
any progress ? does the script work in the buildbot setting, or
does it need tweaking ?
> > Neal Norwitz wrote:
> >
> > > > > > Does that make sense? We would just need /f's script in SVN.
> > > > >
> > > > > in python/Tools/something or sandbox/something ?
> > > >
> > > > python/Doc/tools/som
Stephen J. Turnbull wrote:
> Jason> Filesystem paths are in fact strings on all operating
> Jason> systems I'm aware of.
>
> I have no idea what you could mean by that. The data structure used
> to represent a filesystem on all OS filesystems I've used is a graph
> of directories and file
Martin v. Löwis wrote:
> Sorry, no HTML allowed there.
>
> I created a support request to change/remove the button at
>
> http://sourceforge.net/tracker/index.php?func=detail&aid=1417298&group_id=1&atid=21
instead of spending more time and creativity on a sourceforge account
that's only used
Guido van Rossum wrote:
> Ah. This definitely isn't what ConfigParser was meant to do. I'd think
> for this you should use some kind of XML pickle though. That's
> horrible if end users must edit it, but great for saving
> near-arbitrary persistent data in a readable and occasionally editable
> (f
Donovan Baarda wrote:
> For Python 3000 you could extend this approach to lists and dicts;
> [1,2,3] is a list, f[1,2,3] is a "frozen list" or tuple, {1:'a',2:'b'}
> is a dict, f{1:'a',2:'b'} is a "frozen dict" which can be used as a key
> in other dicts... etc.
Traceback (most recent call last):
Terry Reedy wrote:
> If 3.0 comes with a conversion program, then I would like to see 'lambda'
> replaced with either 'def' or another abbreviation like 'edef' (expression
> def) or 'func'.
making the implied return statment visible might also be a good idea, e.g.
lambda x, y: return x + y
Guido van Rossum wrote:
> IMO asynchat and asyncore are braindead. The should really be removed
> from the standard library. The code is 10 years old and represents at
> least 10-year-old thinking about how to do this.
strange. I'd say it works perfectly fine for what it was designed for
(after
a while ago, I wrote
> > Hopefully something can get hammered out so that at least the Python
> > 3 docs can premiere having been developed on by the whole community.
>
> why wait for Python 3 ?
>
> what's the current release plan for Python 2.5, btw? I cannot find a
> relevant PEP, and the "what
Steve Holden wrote:
> > What is the reason that people want to use threads when they can have
> > poll/select-style message processing? Why does Zope require threads?
> > IOW, why would anybody *want* a "threadsafe patch for asynchat"?
> >
> In case the processing of events needed to block? If I'm
M, Raveendra Babu (STSD) wrote:
> 3)then /usr/ccs/bin/make
>
> it is giving some errors and the error is :
> gcc -c -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict-prototypes
> -I. -I./Include -DPy_BUILD_CORE -o Python/pythonrun.o
> Python/pythonrun.c
> In file included from /usr/include/
Donovan Baarda wrote:
>> Here I think you meant that medusa didn't handle computation in separate
>> threads instead.
>
> No, I pretty much meant what I said :-)
>
> Medusa didn't have any concept of a deferred, hence the idea of using
> one to collect the results of a long computation in another
701 - 732 of 732 matches
Mail list logo
