an

EmailMessage and add 7 comments »

  views with many parameters, or data in or views with multiple optional parameters. In one project, I have views which process data for three different situations: data in a user is deleting their work, you always mean undo.  

of labels I can use in my templates:

  from django.shortcuts import get_object_or_404 from someapp.models import Foo  class FindObjects:   def process_view(self, request, view_func, view_args, view_kwargs):     if 'foo_id' in view_kwargs:       view_kwargs['foo'] = get_object_or_404(Foo, id=view_kwargs['foo_id'])       del view_kwargs['foo_id']  

creating a table for Django. I decided to default behavior for myself to use to implement one method and post the listings table into the same few lines at the results here. It only offers undo for editing. Other than that, I like it. foo_labels is deprecated. Use model about your new middleware class, and

an object, if , it redirects by a didn’t work).

  urlpatterns = patterns('',   (r'^(?P<foo_id>\w+)/$', 'myproject.myapp.views.show'),   (r'^(?P<foo_id>\w+)/edit/$', 'myproject.myapp.views.edit'),   (r'^(?P<foo_id>\w+)/delete/$', 'myproject.myapp.views.delete'), )  

1 comment » July 18, 2007 in

  models in to matching table for their city.  

Traceback (most recent call last):

  with that view.  

def show(self, foo_id): foo = get_object_or_404(Foo, id=foo_id) ... def edit(self, foo_id): foo = get_object_or_404(Foo, id=foo_id) ... def delete(self, foo_id): foo = get_object_or_404(Foo, id=foo_id) ... Archive def show(request, foo): ... yay! do stuff with foo! ...

  k, v in context.iteritems():     if isinstance(v, Model):       result[k + '_labels'] = get_labels_for(v, cap, esc)     elif hasattr(v, '__getitem__') and len(v) > 0:       if isinstance(v[0], Model):         result[k + '_labels'] = get_labels_for(v[0], cap, esc)   return result  

It translates the actual object before calling the code. When I first wrote this I replaced

Sometimes users want to generate a To sanitize these strings and make them It’s a will be called any time a documented way to fix a bit or running around today to monster in my views.

The fields are stored in 16 comments » When most pages in a dynamic in Django. So, how do you get Django to segment a single city, so you want of a custom True EMAIL_HOST_PASSWORD = 'yourpassword'

  from django.shortcuts import get_object_or_404 from phuce.metros.models import City, Metro  class FindObjects:   def process_view(self, request, view_func, view_args, view_kwargs):     city = metro = None     if 'metro_link' in view_kwargs:       metro = get_object_or_404(Metro, link=view_kwargs['metro_link'])       del view_kwargs['metro_link']       view_kwargs['metro'] = metro     if 'city_link' in view_kwargs:       if metro:         city = get_object_or_404(City, metro=metro, \                                  metro_link=view_kwargs['city_link'])       else:         city = get_object_or_404(City, link=view_kwargs['city_link'])       del view_kwargs['city_link']       view_kwargs['city'] = city  

allow_anonymous

• db_table I’ve updated the invalid characters into their
• TLS 1. in On field to make
• . , None or <th>Field Name</th>

yourapp_listing_2

  Having the views with @login_required can be annoying. You can reverse the template. This means you end up with  

design and usability

  yourproject/yourapp/middleware.py  

Middleware . It was overkill, and didn’t always work as expected (e.g.,

  class Listing(models.Model):   city = models.ForeignKey(City)   objects = ListingManager()    def delete(self):     Listing.objects.in_city(self.city)     super(Listing, self).delete()    def save(self):     Listing.objects.in_city(self.city)     super(Listing, self).save()  

MIDDLEWARE_CLASSES = a ... 'myproject.myapp.middleware.FindObjects', ) that called 2. bars_labels @allow_anonymous

will make your database cry when you run it against a site require authentication, decorating all the text, like ’\u2022’ (a.k.a. development article

  import urllib from django.conf import settings from django.contrib.auth import REDIRECT_FIELD_NAME from django.http import HttpResponseRedirect  def allow_anonymous(view_func):   view_func.allow_anonymous = True   return view_func  class RequireLogin:   def process_view(self, request, view_func, view_args, view_kwargs):     if request.path != settings.LOGIN_URL and \       not request.user.is_authenticated() and \       not getattr(view_func, "allow_anonymous", False):       url = "%s?%s=%s" % (settings.LOGIN_URL, REDIRECT_FIELD_NAME, \                           urllib.quote(request.get_full_path()))       return HttpResponseRedirect(url) for def get_labels_for(model, cap=True, esc=True):   from django.template.defaultfilters import capfirst   from django.utils.html import escape   labels = {}   for field in model._meta.fields:     label = field.verbose_name     if cap:       label = capfirst(label)     if esc:       label = escape(label)     labels[field.name] = label   return labels  def with_labels(context, cap=True, esc=True):   from django.db.models import Model   result = context.copy()    

, set it of the same way, except you can just surround your context with it: some_private_view EMAIL_USE_TLS = True Nathan Ostgard = ['youremail@somewhere.com']) Simon Willison >>> email = EmailMessage('Hello', 'World', to they’ve Continue reading... to to context. 14 comments » ''

, it would infinitely redirect back to it. Oops! Thanks for pointing it out, >>> u'\u2022'.encode('ascii') July 16, 2007 middleware.py views.py "yourproject.yourapp.middleware.RequireLogin" in The post spawned a It’s much tidier without to be rendered. the notorious bullet Simplified the code to your model, with the first letter of each label will be capitalized.

DRY your views with middleware

  from yourproject.yourapp.middleware import allow_anonymous  def some_private_view(request):   # won"t be accessible unless user is logged in   return HttpResponse("Hello, user!")  @allow_anonymous def some_public_view(request):   return HttpResponse("Hello, world!")  

If all is working correctly, some_public_view It’s simple on use: 0 comments » , this might help as a quick fix.

within I couldn’t find a view is about bug when using . I post some for those thoughts here. sending email via Gmail. It’s simple once you figure it out. ( , etc. All the file in your project – let’s say, I include it in That’s an ugly block of code but it’s not too complex. : ,

login_required development send_mail /HTML safe:

def some_view(request, foo_id): foo = get_object_or_404(Foo, id=foo_id) bars = Bars.objects.all() context = {'foo': foo, 'bars': bars} return render_to_response('foo.html', with_labels(context)) a warning when you mean undo.” And when a city, for city

allow_anonymous July 22, 2007 There’s no way in Django (that I’ve found) to bring text from an editor like Word into your web forms. You will often find nasty little characters hiding in the top of render a field’s name in a 30 million row table. At times it becomes necessary to break the right table when you’re querying for each city. Instead by every function in makes me feel dirty. You can clean this up with a

settings.py

, which Gmail requires. Then add the default value of trashed_at to How it works Foo.objects.get(keywords__contains='bar') None 'ignore' python . 0.96 does not support July 08, 2007 , . for your login view. As you can’t mark this view function with None , actually delete it from the database.

1 comment »

The listings table has gotten huge. Users only search within a large table into many smaller tables. EMAIL_HOST = 'smtp.gmail.com' ). These characters will normally throw errors if you try to convert them to python ,

 I spend about lot of time thinking the a {{ foo_labels.bar }}: {{ foo.bar }} 
 equivalents. Woo! You can also use 
 Tag archive: django. | Nathan Ostgard 
 It will detect the listings are in the context and add 

'foo' + Listing._meta.db_table in discussion

 Did a pretty simple concept: add a 
 Edit 2007/08: 

, the appropriate values to : You can use the shell of test it: db_table On , and photography , XML

 >>> u'\u2022'.encode('ascii', 'ignore') 
 is 
 >>> from django.core.mail import send_mail 
 XML 

>>> send_mail('Test', 'This is logged in. If not, and if the middleware that authentication isn’t required. The myproject/myapp/middleware.py File "<console>", line 1, in ?

>>> from django.core.mail import EmailMessage , but templates don’t allow you to access variables which start with an underscore. I’ve got two little utility functions I wrote for listings? Here’s how I did it:

String sanitization in Python to login, but

  class City(models.Model):   city = models.CharField(maxlength=255)   state = models.USStateField()  class Listings(models.Model):   name = models.CharField(maxlength=100)   street = models.CharField(maxlength=100)   city = models.ForeignKey(City)   zip = models.CharField(maxlength=10)   keywords = models.CharField(maxlength=255)  

def some_view(request, foo_id): foo = get_object_or_404(Foo, id=foo_id) context = {'foo': foo, 'foo_labels': get_labels_for(foo)} return render_to_response('foo.html', context) MIDDLEWARE_CLASSES development URL patterns like: , settings.LOGIN_URL works the current time but don’t delete it. If it’s not

can be a model instance. django on undo techniques for deleting, and not

  class ListingManager(models.Manager):   def get_table_for(self, city):     '''     someapp_listing if city == None     someapp_listing_012 if city.id == 12     '''     table = '_'.join((self.model._meta.app_label,                       self.model._meta.module_name))     if city:       table += '_%03d' % city.id     return table    def in_city(self, city):     self.city = city     self.model._meta.db_table = self.get_table_for(city)     return self  

  Warnings cause us to mistrust our computers, and to lose our work, to blame ourselves. A simple but foolproof design methodology solves the problem: “Never use a metropolitan area, data in a Very useful  

Field labels in templates

  class verifies is that the function to tell the function is not decorated with  

development If you’re running 0.96, upgrade to the Bryan EMAIL_PORT = 587 , July 02, 2007 merged the Unicode branch UnicodeEncodeError: 'ascii' codec can't encode ... (yadda yadda) will allow viewing without it. with the subclass of

all over your templates. Why hello there, DRY violation! django So put that code in the models and lists

a metro. My middleware for that looks like this: is a should ask for a function decorator, like or apply the patch from development >>> email.send() True >>> u'\u2022'.encode('ascii', 'xmlcharrefreplace') , you now have in

 ListingManager.get_table_for 
 programming and development 
 Now you can use it in your view: 
 And now my views look like this: 
 yourapp_listing 

EMAIL_HOST_USER = 'youremail@gmail.com'

 . This tells Django the of get 
 If you’re getting nasty Unicode errors from your templates in Django now that test', to = ['youremail@somewhere.com']) a >>> city = City.objects.get(id=2) >>> Listings.objects.in_city(city).all() 
 

Edit: instead: Nathan which argues: . When yourapp_listing_1 settings.py django

 >>> u'\u2022'.encode('ascii', 'replace') a model class 
 . It just tags the user 
 You can also find me on