metaclass that inherits a class of that metaclass?

[ironfroggy]

Hoping this isn't seeming too confusing, but I need to create a
metaclass and a class using that metaclass, such that one of the bases
of the metaclass is the class created with that metaclass. I can't
figure out a way to do this, even after trying to add the class as a
base after the classes have been created.

Is there some way I can get this to work properly?

-- 
http://mail.python.org/mailman/listinfo/python-list

Re: metaclass that inherits a class of that metaclass?

[ironfroggy]

because they are representing a seperate typing system outside of
python, to which I am creating a bridge. The metaclass represents the
types of this other system and the class represents the most basic
object type, but since the types the metaclass represent are also
objects, this is the only way i see to represent the relationship
properly.

-- 
http://mail.python.org/mailman/listinfo/python-list

Re: metaclass that inherits a class of that metaclass?

[ironfroggy]

because i need the representations of the other systems types to
themselves be python classes, and so i need a metaclass to make sure
they follow certain rules. This metaclass is for that system what type
is for python, and type is an object, which is a type. same thing, no?

-- 
http://mail.python.org/mailman/listinfo/python-list

python-dev Summary for 2006-12-01 through 2006-12-15

[ironfroggy]

ods of time were
brought up with proposed fixes by patching the rpmlib bindings to
"automagically" poll for any pending calls. An existing patch was suggested but
did not seem to fit the case at hand.

Contributing thread:

- `Polling with Pending Calls? 
<http://mail.python.org/pipermail/python-dev/2006-December/070181.html>`__

-
Cross-compile Patches
-

Patch 1597850 is being actively worked, and will improve the experience when
compiling python for freeBSD from a linux environment.

Contributing thread:

- `cross-compile patches 
<http://mail.python.org/pipermail/python-dev/2006-December/070216.html>`__


Open CPython VM for type information


Would it make sense to modify the CPython virtual machine (bytecode) so that it
was easier for other programs to produce bytecode?  Answer: No -- those programs
should produce either C (which gets called as a function) or python (which gets
interpreted by the python interpreter -- there are already interpreters that
don't use CPython bytecode.

Contributing thread:

- `Open CPython VM for type information 
<http://mail.python.org/pipermail/python-dev/2006-December/070328.html>`__

===
Skipped Threads
===

- `Weekly Python Patch/Bug Summary 
<http://mail.python.org/pipermail/python-dev/2006-December/070119.html>`__
- `Windows SDK 
<http://mail.python.org/pipermail/python-dev/2006-December/070308.html>`__
- `help for a noob - version for a sharp ARM 
<http://mail.python.org/pipermail/python-dev/2006-December/070286.html>`__
- `fileinput module tests 
<http://mail.python.org/pipermail/python-dev/2006-December/070307.html>`__
- `fpectl: does a better implementation make sense? 
<http://mail.python.org/pipermail/python-dev/2006-December/070118.html>`__
- `Small tweak to tokenize.py? 
<http://mail.python.org/pipermail/python-dev/2006-December/070127.html>`__
- `features i'd like [Python 3000] ... #3: fix super() 
<http://mail.python.org/pipermail/python-dev/2006-December/070168.html>`__
- `Makefile.pre.in Patch 
<http://mail.python.org/pipermail/python-dev/2006-December/070172.html>`__
- `Python and LSB: Meeting Report 
<http://mail.python.org/pipermail/python-dev/2006-December/070186.html>`__
- `Virtual Python (was Re: Python and the Linux Standard Base (LSB)) 
<http://mail.python.org/pipermail/python-dev/2006-December/070194.html>`__
- `DRAFT: python-dev summary for 2006-11-16 through 2006-11-30 
<http://mail.python.org/pipermail/python-dev/2006-December/070229.html>`__
- `Looking for new Python-Dev Summarizers 
<http://mail.python.org/pipermail/python-dev/2006-December/070232.html>`__
- `Adding C99 bool to struct module 
<http://mail.python.org/pipermail/python-dev/2006-December/070276.html>`__
- `Spam and semi-spam and neo-spam 
<http://mail.python.org/pipermail/python-dev/2006-December/070284.html>`__
- `Next PyPy sprint: Leysin 8-14th January 2007 
<http://mail.python.org/pipermail/python-dev/2006-December/070217.html>`__
- `Distribution tools: What I would like to see 
<http://mail.python.org/pipermail/python-dev/2006-December/070234.html>`__
- `RealClearPolitics - Articles - Exit Rumsfeld, Smiling 
<http://mail.python.org/pipermail/python-dev/2006-December/070283.html>`__






Epilogue


This is a summary of traffic on the `python-dev mailing list`_ from
December 01, 2006 through December 15, 2006.
It is intended to inform the wider Python community of on-going
developments on the list on a semi-monthly basis.  An archive_ of
previous summaries is available online.

An `RSS feed`_ of the titles of the summaries is available.
You can also watch comp.lang.python or comp.lang.python.announce for
new summaries (or through their email gateways of python-list or
python-announce, respectively, as found at http://mail.python.org).

This python-dev summary is the 1st written by Calvin Spealman.

To contact me, please send email:

- Calvin Spealman (ironfroggy at gmail dot com)

Do *not* post to comp.lang.python if you wish to reach me.

The `Python Software Foundation`_ is the non-profit organization that
holds the intellectual property for Python.  It also tries to advance
the development and use of Python.  If you find the python-dev Summary
helpful please consider making a donation.  You can make a donation at
http://python.org/psf/donations.html .  Every cent counts so even a
small donation with a credit card, check, or by PayPal helps.



Commenting on Topics


To comment on anything mentioned here, just post to
`comp.lang.python`_ (or email python-list@python.org which is a
gateway to the newsgroup) with a subject line mentioning what you are
discussing.  All python-dev members are interested in seeing ideas
discussed by the community, so