(on python-dev) Kristján V. Jónsson wrote:
> We have been using gc.get_objects() but it has several problems:
> 1) ... results in a list so long that it often kills the system.
In Py3K, should this also return an iterator, rather than a list?
In other words, is the dict.items change something s
On 1/24/07, Jim Jewett <[EMAIL PROTECTED]> wrote:
> (on python-dev) Kristján V. Jónsson wrote:
>
> > We have been using gc.get_objects() but it has several problems:
> > 1) ... results in a list so long that it often kills the system.
>
> In Py3K, should this also return an iterator, rather than a
i'm having great trouble in RPyC with pickling object proxies.
several users have asked for this feature, but no matter how hard
i try to "bend the truth", pickle always complains. it uses
type(obj) for the dispatching, which "uncovers" the object
is actually a proxy, rather than a real object.
re
On 1/23/07, Giovanni Bajo <[EMAIL PROTECTED]> wrote:
> On 22/01/2007 23.45, Collin Winter wrote:
>
> > target, thus eliminating the reference cycle. The source-to-source
> > translation, as suggested by Phillip J. Eby [#except-translation]_ is
> > ::
> >
> > try:
> > ...
> > except
On 1/23/07, Brett Cannon <[EMAIL PROTECTED]> wrote:
> I just realized I misread your paragraph and took E to represent an
> exception class, not a nebulous object that could be an exception
> class or instance.
That's what I figured. Is it clearer if E is changed to EXCEPTION?
"""
2. ``raise EXCE
On Wed, Jan 24, 2007, tomer filiba wrote:
>
> i'm having great trouble in RPyC with pickling object proxies. several
> users have asked for this feature, but no matter how hard i try to
> "bend the truth", pickle always complains. it uses type(obj) for the
> dispatching, which "uncovers" the object
