I'm not sure about introducing a special syntax for accessing
dictionary entries, array elements and/or object attributes *within a
string formatter*... much less an overloaded one that differs from
how these elements are accessed in "regular python".
> Compound names are a sequence of
Some thoughts from a lurker, largely concerning syntax; discount as
you wish.
First:
> Keyword-only arguments are not required to have a default value.
> Since Python requires that all arguments be bound to a value,
> and since the only way to bind a value to a keyword-only argume
Hello folks,
I just ran all the test iterations Martin suggested on Py2.5a1.
That is, I did a normal build and ran 'make test', then installed and
ran 'import test.regrtest; test.regrtest.main()', and then I did the
whole thing over again with a framework build and install. All four
test ru
On Apr 4, 2006, at 1:29 AM, Martin v. Löwis wrote:
> Zachary Pincus wrote:
>> Specifically, this patch would change a core python code path.
>
> Why do you think so? I believe Python always passes absolute paths
> to dlopen, so any path resolution dlopen might do should be
&
> Thanks for reminding us about this issue.
> Unfortunately, without an explicit ok from one of the Mac maintainers,
> I don't want to add this myself. If you can get Bob, Ronald, or Jack
> to say ok, I will apply the patch ASAP. I have a Mac OS X.4 box and
> can test it, but don't know the suita
Hi folks,
I submitted a patch a little while ago to led Python on Darwin/OS X
use the same code path to load extensions it uses on most other Unix-
like platforms. (The reasons for this are several, and mentioned in
the patch: http://sourceforge.net/tracker/index.php?
func=detail&aid=1454844
