Thomas Heller:
> Not only that, all the other flags like -O and -E are also in sys.argvu
> but not in sys.argv.
OK, new patch fixes these and the "-c" issue.
> Those are nearly obsoleted by the subprocess module (although I do not
> know how that handles unicode.
It breaks. The argspec is
Nothing to say, just keep up the good work! I hope the triple-team
approach is still working well.
--
Aahz ([EMAIL PROTECTED]) <*> http://www.pythoncraft.com/
f u cn rd ths, u cn gt a gd jb n nx prgrmmng.
___
Python-Dev mailing list
P
Phillip J. Eby wrote:
> Expand your mind. :) "Resource" can include whatever objects you
> want it
> to -- or no objects at all. A resource can be conceptual - like for
> example the user's attention, or the contents of a status bar or log
> message, or the timing/profiling of an activity. I t
Here's our draft of the summary for the second half of June. As
usual, please let me, Tony or Tim know if you have any comments or
corrections.
-- Steven Bethard
=
Summary Announcements
=
--
OSCON Registration
--
Though if
Neil Hodgson <[EMAIL PROTECTED]> writes:
> Thomas Heller:
>
>> OTOH, Python is lacking a lot when you have to handle unicode strings on
>> sys.path, in command line arguments, environment variables and maybe
>> other places.
>
>A new patch #1231336 "Add unicode for sys.argv, os.environ,
> os
On 7/2/05, Aahz <[EMAIL PROTECTED]> wrote:
> Sounds like a better way to go is a Money package (or perhaps a Financial
> package) and just create the Currency module within it for now. Anyway,
Something to consider!
> given that this isn't going to be a real PEP any time soon, please
> restric
[Phillip J. Eby]
>
> with context_expression as variable:
> # perform actions within a context
>
> The "with" statement establishes a context in which some operations
are to
> be performed. Often, this is a resource management context, wherein
some
> resource is allocated when the context is
On 4 Jul 2005, at 18:59, Raymond Hettinger wrote:
> P.S. I still don't follow the whole yours/mine comment from Michael.
> The offending code line was part of 2.136 which CVS says was checked-in
> by him on 5/27/2005 and then fixed by him on 6/30/2005.
Well, my confusion started and ended with t
> Alas, a typical exchange. The checkins are mailed from the committer's
> Sf email address, but the mailing list has been set up to redirect all
> replies to python-dev -- if you don't catch this before sending, you
> may be embarrassed in public or confuse the addressee.
>
> Is this behavior of
At 11:48 PM 7/3/2005 -0400, Raymond Hettinger wrote:
>Remember,
>these methods are going to show up in objects such as Context which are
>not primarily about 343. All of the other methods names will have
>nothing to do with 343, so our choice of magic names needs to be really
>good (as there will
[Raymond Hettinger]
> > I'm getting a compiler warning from your checkin:
[Michael Hudson]
> "your"? Mine?
Alas, a typical exchange. The checkins are mailed from the committer's
Sf email address, but the mailing list has been set up to redirect all
replies to python-dev -- if you don't catch thi
Take II on some draft docs (accuracy of specific examples obviously
depends on other PEP 343 and PEP 342 related updates).
Based on the various discussions, the following suggests the term
"suite managers". That focuses on the fact that we're doing something
before and after the contained suite
Raymond Hettinger wrote:
> There is no value in expanding a concept to the point of being
> meaningless (i.e. meaning whatever you want it to or nothing at all).
> Instead, we need a phrase that expresses the essence of the following:
>
>
> abc = EXPR
> exc = (None, None, None)
>
> Guido van Rossum:
> > Then maybe the code that handles Unicode paths in arguments should be
> > fixed rather than adding a module that encapsulates a work-around...
On 7/3/05, Neil Hodgson <[EMAIL PROTECTED]> wrote:
>It isn't clear whether you are saying this should be fixed by the
> user or
"Raymond Hettinger" <[EMAIL PROTECTED]> writes:
> Another trouble with "resource managed" is that it makes little sense
> even when describing something that is clearly a resource (for instance,
> "locking objects are resource managed", what the heck could that mean,
> there is no hint about the p
15 matches
Mail list logo
