On May 4, 2005, at 6:13 PM, has wrote:
> Bob wrote:
>
>
>>> I figured that, but I'd rather hoped a more elegant solution
>>> might be forthcoming at source. Is there a good reason why they
>>> couldn't both agree on a common location, or at least provide the
>>> relevant aliases in 2.4 to p
Bob wrote:
>>I figured that, but I'd rather hoped a more elegant solution might be
>>forthcoming at source. Is there a good reason why they couldn't both agree on
>>a common location, or at least provide the relevant aliases in 2.4 to
>>preserve Python's much-vaunted backwards compatibility?
>
On May 4, 2005, at 4:50 PM, has wrote:
> Bob wrote:
>
>
>>> Probably one for Bob, but there's an unpleasant disagreement
>>> between Py23Compat and Python 2.4 [which] means scripts written
>>> on Python 2.3 break on 2.4 and vice-versa when importing any of
>>> these modules. What's the fix?
Bob wrote:
>>Probably one for Bob, but there's an unpleasant disagreement between
>>Py23Compat and Python 2.4 [which] means scripts written on Python 2.3 break
>>on 2.4 and vice-versa when importing any of these modules. What's the fix?
>
>This is not a bug,
Maybe not, but it's hardly good desi
On May 4, 2005, at 3:21 PM, has wrote:
> Probably one for Bob, but there's an unpleasant disagreement
> between Py23Compat and Python 2.4 on where the LaunchServices, OSA,
> and other new 2.4 modules are located: the former installs them in
> individual directories of the same name under si
Hi all,
Probably one for Bob, but there's an unpleasant disagreement between Py23Compat
and Python 2.4 on where the LaunchServices, OSA, and other new 2.4 modules are
located: the former installs them in individual directories of the same name
under site-packages, the later keeps them at the to
