Every now and then, the computer gods smile and give me a freebie.<\/p>\n
I’ve been worrying my mind out over a few problems \/ obstacles for my Review Board extensions GSoC project<\/a>.\u00a0 In particular, I’ve been worrying about dealing with extension dependencies, conflicts, and installation.<\/p>\n I racked my brain.\u00a0 I came up with scenarios.\u00a0 I drew lots of big scary diagrams on a wipe board.<\/p>\n And then light dawned.<\/p>\n Enter Setuptools<\/a> and Python Eggs<\/a>.<\/p>\n All of those things I was worried about having to build and account for?\u00a0 When using Python Eggs, It’s all built in.<\/em> Dependencies?\u00a0 Taken care of. Conflicts?\u00a0 Don’t worry about it.\u00a0 Installation?\u00a0 That’s what Setuptools and Python Eggs were built for!<\/p>\n In fact, it even looks like Setuptools was designed with extensible applications in mind.<\/a><\/p>\n Here’s the setup.py file for the rb-reports extension in the rb-extensions-pack on Github:<\/a><\/p>\n Pay particular attention to the “entry_points” parameter.\u00a0 What this is doing, is registering rbreports.extension:ReportsExtension to the entry point “reviewboard.extensions”.<\/p>\n “Hold up!”, I hear you asking. “What’s an entry point?”<\/p>\n An entry point is a unique identifier associated with an application that can accept extensions.<\/p>\n The unique identifier for Review Board extensions is “reviewboard.extensions”.<\/p>\n This is the first handshake, more or less, between Review Board and any extensions:\u00a0 in order for Review Board to “see” the extension, the extension must register an entry point at “reviewboard.extensions”.<\/p>\n This blog post shows how extensions can be found and loaded up.<\/a><\/p>\n I remember also being worried about how to create tables in Django for extension models.\u00a0 I thought “holy smokes, I’m going to have to either shoehorn some raw SQL into the extension manager, or maybe even trust the extension developers to write the CREATE TABLE queries themselves!”.<\/p>\n Luckily, there’s a better alternative.<\/p>\n Django knows about its applications through a dictionary called INSTALLED_APPS.<\/a> When you add a new model to a Django project, you simply add the model app to the INSTALLED_APPS dictionary, and run “manage.py syncdb”.\u00a0 Django does the magic, bingo-bango, and boom – tables created.<\/p>\n So if a new extension has some tables it needs created, I simply insert the app name of the extension into INSTALLED_APPS when the extension is installed, and call syncdb programmatically<\/a>.\u00a0 Tables created:\u00a0 no sweat.<\/p>\n Creating tables is easy.\u00a0 But what if an extension gets updated, and the table needs to be modified?\u00a0 Sounds like we’ve got a mess on our hands.<\/p>\n And don’t expect Django to save you.\u00a0 When you modify a model in Django, they expect you to into that DB and alter that table by hand:<\/p>\n [syncdb] creates the tables if they don\u2019t yet exist. Note that syncdb does not<\/em> sync changes in models or deletions of models; if you make a change to a model or delete a model, and you want to update the database, syncdb will not handle that. Thankfully, there’s a mechanism that’s already built into Review Board that makes this trouble go away:\u00a0 django-evolution<\/a>.\u00a0 Django-evolution, when used properly, will automatically detect changes in application models, and alter the database tables accordingly.\u00a0 This is how Review Board does upgrades.<\/p>\nBatteries Come Included<\/h3>\n
Wait, really?\u00a0 How?<\/h3>\n
from setuptools import setup, find_packages\r\n\r\nPACKAGE=\"RB-Reports\"\r\nVERSION=\"0.1\"\r\n\r\nsetup(\r\n name=PACKAGE,\r\n version=VERSION,\r\n description=\"\"\"Reports extension for Review Board\"\"\",\r\n author=\"Christian Hammond\",\r\n packages=[\"rbreports\"],\r\n entry_points={\r\n 'reviewboard.extensions':\r\n '%s = rbreports.extension:ReportsExtension' % PACKAGE,\r\n },\r\n package_data={\r\n 'rbreports': [\r\n 'htdocs\/css\/*.css',\r\n 'htdocs\/js\/*.js',\r\n 'templates\/rbreports\/*.html',\r\n 'templates\/rbreports\/*.txt',\r\n ],\r\n }\r\n)\r\n<\/pre>\nEntry Points<\/h3>\n
Other Goodies<\/h3>\n
INSTALLED_APPS and Django<\/h4>\n
django-evolution<\/h4>\n
\nFrom The Django Book<\/a> – Chapter 5: Models<\/a><\/p><\/blockquote>\n