Comments on: So does this exception come with a map, and some food? http://jessenoller.com/2008/08/08/so-does-this-exception-come-with-a-map-and-some-food/ python, programming and other things Sun, 04 Mar 2012 06:06:00 +0000 hourly 1 By: Pawel Murias http://jessenoller.com/2008/08/08/so-does-this-exception-come-with-a-map-and-some-food/comment-page-1/#comment-139223 Pawel Murias Sat, 09 Aug 2008 01:14:35 +0000 http://jessenoller.com/?p=291#comment-139223 The error sounds perfectly reasonable if you know what metaclasses are and provided it's an issue with them The error sounds perfectly reasonable if you know what metaclasses are and provided it’s an issue with them

]]> By: Kevin Smith http://jessenoller.com/2008/08/08/so-does-this-exception-come-with-a-map-and-some-food/comment-page-1/#comment-139222 Kevin Smith Fri, 08 Aug 2008 22:40:10 +0000 http://jessenoller.com/?p=291#comment-139222 ROFL that's awesome. ROFL that’s awesome.

]]> By: jnoller http://jessenoller.com/2008/08/08/so-does-this-exception-come-with-a-map-and-some-food/comment-page-1/#comment-139221 jnoller Fri, 08 Aug 2008 21:42:22 +0000 http://jessenoller.com/?p=291#comment-139221 Yes, this stems from fubaring your inheritance/metaclasses. Interestingly enough plug/ there was a pymag article this past month trying to demystify metaclasses: I highly recommend it /plug. Of course, you're right - the error should match the difficulty of the code.<br><br>Of course, where does that put something like threading? "Error: No, don't share state, you're screwed anyways. Quit now" :) Yes, this stems from fubaring your inheritance/metaclasses. Interestingly enough plug/ there was a pymag article this past month trying to demystify metaclasses: I highly recommend it /plug. Of course, you’re right — the error should match the difficulty of the code.

Of course, where does that put something like threading? “Error: No, don’t share state, you’re screwed anyways. Quit now” :)

]]> By: Doug Napoleone http://jessenoller.com/2008/08/08/so-does-this-exception-come-with-a-map-and-some-food/comment-page-1/#comment-139220 Doug Napoleone Fri, 08 Aug 2008 21:34:57 +0000 http://jessenoller.com/?p=291#comment-139220 The error thrown need only be one order of magnitude easier to understand than the language feature you are using which is causing the problem. Given that this is python metaclasses we are talking about, I would say that the error message is much clearer than expected ;-)<br><br>I cant remember where I last saw this error, but it was eather caused by multiple inheritance (with metaclasses and improper super use when dealing with them), and/or mixing old and new style classes with metaclasses. Remember your (object).<br><br>I would be interested to see the code causing the problem, and what the actual issue is.<br>But then again, I don't think I want to hurt my head like that.... The error thrown need only be one order of magnitude easier to understand than the language feature you are using which is causing the problem. Given that this is python metaclasses we are talking about, I would say that the error message is much clearer than expected ;-)

I cant remember where I last saw this error, but it was eather caused by multiple inheritance (with metaclasses and improper super use when dealing with them), and/or mixing old and new style classes with metaclasses. Remember your (object).

I would be interested to see the code causing the problem, and what the actual issue is.
But then again, I don’t think I want to hurt my head like that.…

]]> By: Pawel Murias http://jessenoller.com/2008/08/08/so-does-this-exception-come-with-a-map-and-some-food/comment-page-1/#comment-62351 Pawel Murias Fri, 08 Aug 2008 21:14:35 +0000 http://jessenoller.com/?p=291#comment-62351 The error sounds perfectly reasonable if you know what metaclasses are and provided it's an issue with them The error sounds perfectly reasonable if you know what metaclasses are and provided it’s an issue with them

]]> By: Kevin Smith http://jessenoller.com/2008/08/08/so-does-this-exception-come-with-a-map-and-some-food/comment-page-1/#comment-62350 Kevin Smith Fri, 08 Aug 2008 18:40:10 +0000 http://jessenoller.com/?p=291#comment-62350 ROFL that's awesome. ROFL that’s awesome.

]]> By: jnoller http://jessenoller.com/2008/08/08/so-does-this-exception-come-with-a-map-and-some-food/comment-page-1/#comment-62349 jnoller Fri, 08 Aug 2008 17:42:22 +0000 http://jessenoller.com/?p=291#comment-62349 Yes, this stems from fubaring your inheritance/metaclasses. Interestingly enough plug/ there was a pymag article this past month trying to demystify metaclasses: I highly recommend it /plug. Of course, you're right - the error should match the difficulty of the code.<br><br>Of course, where does that put something like threading? "Error: No, don't share state, you're screwed anyways. Quit now" :) Yes, this stems from fubaring your inheritance/metaclasses. Interestingly enough plug/ there was a pymag article this past month trying to demystify metaclasses: I highly recommend it /plug. Of course, you’re right — the error should match the difficulty of the code.

Of course, where does that put something like threading? “Error: No, don’t share state, you’re screwed anyways. Quit now” :)

]]> By: Doug Napoleone http://jessenoller.com/2008/08/08/so-does-this-exception-come-with-a-map-and-some-food/comment-page-1/#comment-62348 Doug Napoleone Fri, 08 Aug 2008 17:34:57 +0000 http://jessenoller.com/?p=291#comment-62348 The error thrown need only be one order of magnitude easier to understand than the language feature you are using which is causing the problem. Given that this is python metaclasses we are talking about, I would say that the error message is much clearer than expected ;-)<br><br>I cant remember where I last saw this error, but it was eather caused by multiple inheritance (with metaclasses and improper super use when dealing with them), and/or mixing old and new style classes with metaclasses. Remember your (object).<br><br>I would be interested to see the code causing the problem, and what the actual issue is.<br>But then again, I don't think I want to hurt my head like that.... The error thrown need only be one order of magnitude easier to understand than the language feature you are using which is causing the problem. Given that this is python metaclasses we are talking about, I would say that the error message is much clearer than expected ;-)

I cant remember where I last saw this error, but it was eather caused by multiple inheritance (with metaclasses and improper super use when dealing with them), and/or mixing old and new style classes with metaclasses. Remember your (object).

I would be interested to see the code causing the problem, and what the actual issue is.
But then again, I don’t think I want to hurt my head like that.…

]]>