On Apr 26, 11:25 am, rusi wrote:
> To present these kind of errors, Erlang has a concept of sticky
> modules -- those that come from the system…
??present?? should have been 'prevent'
--
http://mail.python.org/mailman/listinfo/python-list
On Apr 26, 11:04 am, Tim Roberts wrote:
> Forafo San wrote:
>
> >OK, lesson learned: Take care not to have module names that conflict with
> >python's built ins. Sorry for being so obtuse.
>
> You don't have to apologize. We've all been bitten by this at least once.
Yes…
When it comes to keywo
Forafo San wrote:
>
>OK, lesson learned: Take care not to have module names that conflict with
>python's built ins. Sorry for being so obtuse.
You don't have to apologize. We've all been bitten by this at least once.
--
Tim Roberts, t...@probo.com
Providenza & Boekelheide, Inc.
--
http://mail
On Wednesday, April 24, 2013 3:08:27 PM UTC-4, Neil Cerutti wrote:
> On 2013-04-24, Forafo San wrote:
>
> > Hello All,
>
> > I'm running Python version 2.7.3_6 on a FreeBSD system. The following
> > session in a Python interpreter throws a mysterious TypeError:
>
> >
>
> > ---
Hello All,
I'm running Python version 2.7.3_6 on a FreeBSD system. The following session
in a Python interpreter throws a mysterious TypeError:
--
[ppvora@snowfall ~/xbrl]$ python
Python 2.7.3 (default, Apr 22 2013, 18:42:18)
[GCC 4.2.1 20070719 [FreeBSD
On 2013-04-24, Forafo San wrote:
> Hello All,
> I'm running Python version 2.7.3_6 on a FreeBSD system. The following session
> in a Python interpreter throws a mysterious TypeError:
>
> --
> [ppvora@snowfall ~/xbrl]$ python
> Python 2.7.3 (default, Apr 22
