Am 31.08.2012 11:45, schrieb Juha Jeronen:
Apart from that, it seems that sympy.core.core.ClassRegistry must be
filtered out separately, and sympy.ntheory.generate.Sieve (a classobj
with no __name__ or __class__, neither str() nor repr() matching the
sympifiable string) must be handled as a special case.
That one is supposed to be an implementation detail. It's providing the
implementation for a singleton, namely "the" Sieve of Erasthotenes.
That's the view for SymPy-using code anyway; some tests that check
caching internals of Sieve do indeed create multiple instances.
I suspect you don't want such classes in your results.
However, I have not idea how to detect that category. Checking for a
__name__ or __class__ might fit or not; maybe some better convention
exists, or should be created. Aaron or Ondrej should be able to answer that.
--
You received this message because you are subscribed to the Google Groups
"sympy" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sympy?hl=en.
