On 08:44 pm, [EMAIL PROTECTED] wrote:
On Mon, Oct 27, 2008 at 1:30 PM, Nick Coghlan <[EMAIL PROTECTED]>
wrote:
If the current system is setting __path__ to a string in frozen
packages, I'd have to wonder how well any existing __path__
manipulation
tools handle frozen packages without special
Brett Cannon wrote:
> Beats me. At this point I am only implementing them for
> backwards-compatibility, but they are exposing some inconsistencies in
> how various aspects of import are implemented. If I had my way they
> would be an optional thing that you would have to explicitly put on
> sys.me
On Mon, Oct 27, 2008 at 1:30 PM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
>> On 07:24 pm, [EMAIL PROTECTED] wrote:
>>> On Mon, Oct 27, 2008 at 3:50 AM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
Brett Cannon wrote:
>>
>>> Good enough for me. Then I am just going to ignor
[EMAIL PROTECTED] wrote:
> On 07:24 pm, [EMAIL PROTECTED] wrote:
>> On Mon, Oct 27, 2008 at 3:50 AM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
>>> Brett Cannon wrote:
>
>> Good enough for me. Then I am just going to ignore the 'path' argument
>> for frozen modules but use it to short-circuit imports
On 08:24 pm, [EMAIL PROTECTED] wrote:
On Mon, Oct 27, 2008 at 12:31 PM, <[EMAIL PROTECTED]> wrote:
On 07:24 pm, [EMAIL PROTECTED] wrote:
On Mon, Oct 27, 2008 at 3:50 AM, Nick Coghlan <[EMAIL PROTECTED]>
wrote:
For what it's worth, Twisted uses the __path__ attribute to facilitate
its
plu
On Mon, Oct 27, 2008 at 1:22 PM, <[EMAIL PROTECTED]> wrote:
> Python's configure.in contains this check:
>
># disable check for icc since it seems to pass, but generates a warning
>if test "$CC" = icc
>then
> ac_cv_opt_olimit_ok=no
>fi
>
>AC_MSG_CHECKING(whether $CC accept
On Mon, Oct 27, 2008 at 1:03 PM, Thomas Heller <[EMAIL PROTECTED]> wrote:
> Brett Cannon schrieb:
>> I just discovered frozen packages set their __path__ simply to their
>> name and not to a list as expected (http://bugs.python.org/issue4211).
>> This made me think about the 'path' argument to find
On Mon, Oct 27, 2008 at 12:31 PM, <[EMAIL PROTECTED]> wrote:
> On 07:24 pm, [EMAIL PROTECTED] wrote:
>>
>> On Mon, Oct 27, 2008 at 3:50 AM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
>>>
>>> Brett Cannon wrote:
>
>> Good enough for me. Then I am just going to ignore the 'path' argument
>> for frozen
Python's configure.in contains this check:
# disable check for icc since it seems to pass, but generates a warning
if test "$CC" = icc
then
ac_cv_opt_olimit_ok=no
fi
AC_MSG_CHECKING(whether $CC accepts -OPT:Olimit=0)
AC_CACHE_VAL(ac_cv_opt_olimit_ok,
[ac_save_cc=
Brett Cannon schrieb:
> I just discovered frozen packages set their __path__ simply to their
> name and not to a list as expected (http://bugs.python.org/issue4211).
> This made me think about the 'path' argument to find_module() and
> whether it can be treated as simply a hint or should always be
On 07:24 pm, [EMAIL PROTECTED] wrote:
On Mon, Oct 27, 2008 at 3:50 AM, Nick Coghlan <[EMAIL PROTECTED]>
wrote:
Brett Cannon wrote:
Good enough for me. Then I am just going to ignore the 'path' argument
for frozen modules but use it to short-circuit imports for built-in
modules.
For what it'
On Mon, Oct 27, 2008 at 3:50 AM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> Brett Cannon wrote:
>> I just discovered frozen packages set their __path__ simply to their
>> name and not to a list as expected (http://bugs.python.org/issue4211).
>> This made me think about the 'path' argument to find_mo
Brett Cannon wrote:
> I just discovered frozen packages set their __path__ simply to their
> name and not to a list as expected (http://bugs.python.org/issue4211).
> This made me think about the 'path' argument to find_module() and
> whether it can be treated as simply a hint or should always be
>
13 matches
Mail list logo
