[sage-combinat-devel] Re: __classcall_private__ in partitions

2013-03-04 Thread Travis Scrimshaw
Hey Simon, Because the ABC Partitions has a __classcall_private__() which returns the correct parent and is acting as a factory. This is applied to all of its subclasses which doesn't make sense there and caused exceptions to be raised (at least, that's what I remember, it's been awhile

[sage-combinat-devel] Re: __classcall_private__ in partitions

2013-03-04 Thread Simon King
Hi Travis, On 2013-03-04, Travis Scrimshaw tsc...@ucdavis.edu wrote: Because the ABC Partitions has a __classcall_private__() which returns the correct parent and is acting as a factory. This is applied to all of its subclasses No, certainly not. From the docs of

[sage-combinat-devel] Re: __classcall_private__ in partitions

2013-03-04 Thread Travis Scrimshaw
Hey Simon, No, certainly not. From the docs of sage.misc.classcall_metaclass: Another difference is that ``__classcall__`` is inherited by subclasses, which may be desirable, or not. If not, one should instead define the method ``__classcall_private__`` which will

[sage-combinat-devel] Re: __classcall_private__ in partitions

2013-03-04 Thread Simon King
Hi Travis, On 2013-03-04, Travis Scrimshaw tsc...@ucdavis.edu wrote: I most likely messed something up when I was doing this the first time through...I had a pickling issue come up with number of arguments with the classcalls vs. __init__, but I think I solved that differently... Number of

[sage-combinat-devel] Re: __classcall_private__ in partitions

2013-03-04 Thread Simon King
Hi! On 2013-03-04, Simon King simon.k...@uni-jena.de wrote: Could you send me the patch with your changes (since trac is currently down, we can't create the followup ticket)? I am confident the server will soon enough be up. If it isn't by tomorrow, I'll send you the patch. See #14225.