Re: Propagating X-Frame-Options header to debug view responses on errors

iews are called, and if they error. Alternatively your middleware > might just set X-Frame-Options for all url's with the prefix your app is > installed at. > > On Mon, 24 Jan 2022 at 16:17, 'Ben Dickinson' via Django developers > (Contributions to Django itself) wrote

Propagating X-Frame-Options header to debug view responses on errors

be happy to have a go at this, but from a quick look it's not trivial. Any thoughts about whether this would be desirable or even possible and guidance about how I might start would be very gratefully received! Cheers, Ben -- You received this message because you are subscribed to t

Re: New deferred loading implementation (Was: [Review Request] Added support for database delegated fields (like AutoField))

This is what I wanted to know. I am willing to take on starting this DEP, with the caveat I've not done one before, and it will almost certainly require many revisions. On Tuesday, 8 November 2016 15:32:48 UTC, Marc Tamlyn wrote: > > I have fed a lot into this discussion in person and on Slack.

Re: New deferred loading implementation (Was: [Review Request] Added support for database delegated fields (like AutoField))

As discussed with many core team members (Simon Charette, Josh Smeaton, Marc Tamlyn, Tim Graham) at DUTH 2016 sprints, myself and Joachim Jablon have proposed a new, simpler solution to this. See https://code.djangoproject.com/ticket/27446 The proposal therefore is to add a `readonly` option to

Re: Django Model Fields a repr_output property, to include a field in the string representation of an object

Well in that case wouldn't it make sense to add it to the meta class? Just like how there's unique_together, etc., there could be repr_fields. In which case I think it would be great if it were part of Django. Maybe reconsider as a part of the meta class? Ben Friedland www.bugb

Django Model Fields a repr_output property, to include a field in the string representation of an object

): first_name = models.CharField(max_length=50) last_name = models.CharField(max_length=50) >>> person = Person(first_name='Ben', last_name='Friedland') >>> print person # fairly useless object representation This feature would work something like: class

Re: Scaling Django for Multiple Teams

My bad--see you guys on the other side. -Ben On Mon, Apr 18, 2016 at 5:31 PM, Tim Graham wrote: > This mailing list is for the development of Django itself. Please use > django-users for usage questions. Is there some place we could improve that > would have helped you identify th

Re: Revisiting lazy middleware initialization

0+ minutes. Just weighing in on the general design principle of long initial lazy loads in frameworks. -Ben On Sun, Mar 27, 2016 at 3:42 PM, Fred Stluka wrote: > Ben, > > If lazy loading is causing you problems, here's good info on how to > force Django to load ever

Re: MySQL data loss possibility with concurrent ManyToManyField saves

What's the current status on this? Is the .for_update() change mentioned in the bug report the best way to go? Is anyone working on a PR? On 03/18/2016 05:15 PM, Karen Tracey wrote: This is the 2nd major issue I can recall caused by MySQL default of REPEATABLE READ transaction isolation level.

Re: PostGres 9.5 Upsert

Hey--that's pretty slick. I'm not sure when we're going to take a shot at this implementation, but I'll keep that in mind. -Ben On Mon, Feb 1, 2016 at 7:12 AM, wrote: > It should be possible to use a "RETURNING" clause to get the new row even > in th

Re: MOSS Award to Django

ts I mean this example sounds like celery to me. You don't want an image to maybe have a thumbnail generated. And you have no return value to the client when the thumbnail is generated. -Ben On Tue, Dec 15, 2015 at 3:41 PM, Shai Berger wrote: > On Wednesday 16 December 2015 01:07:16 Ben Li

Re: MOSS Award to Django

ten on all relevant channels and run consumer code when a message is ready. I get that the goal of this is for asynchronous web requests, but if it's generalized right it seems like it could cover doing any kind of work without the pressure of completing a web transaction in a timely fashio

[Feature] On CommandError, sys.exit(1)

is supplied). I can do the PR for the CommandError thing (unless anyone sees a reason not to, or that would not work/there is a better place to put it). -- *Ben Liyanage *|* Software Engineer *|* Rentlytics, Inc.* Phone: (410) 336-2464 | Email: bliyan...@rentlytics.com 1132 Howard Street, San Franci

Re: Feature idea: Add support for PostgreSQL's COPY command in contrib.postgres

Glad you're interested! 1. Yes you can. You can use the field or model method transformations to provide any SQL you'd like. PostgreSQL has a to_timestamp

Feature idea: Add support for PostgreSQL's COPY command in contrib.postgres

er refactoring and additional coding is necessary to qualify it for a merge. Please let me know what you think. And if I've overlooked some previous discussion or superior third-party library in this area, please forgive me. I searched around but was unable to find anything. Sincerely,

Re: Remove autogenerated 'id' when using existing database

It is true that the table doesn't have a primary key. 1, I might be able to talk to the DBA to add a primary key in here and re-sync the class. But is that required for each table to have pk to run Django? 2, what if I just modify the class to have fake pk =True, but not modify the database st

Remove autogenerated 'id' when using existing database

r unmanaged class. Please confirm and decide whether to patch this into your code base. Thanks. Ben Lin http://benincampus.blogspot.com -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To un

one patch to fix a Django 1.8 issue for merging legacy database

Issue: I have an existing database, so the guide in https://docs.djangoproject.com/en/1.8/howto/legacy-databases/ to inspect db and created models.py . That table does NOT have an 'id' column, and the created models.py doesn't have 'id' either, and the class is unmanaged (managed=False). But w

Re: does django-admin need a man page?

t whatever idiosyncratic help system it prefers me to use. -- \“Most people, I think, don't even know what a rootkit is, so | `\ why should they care about it?” —Thomas Hesse, Sony BMG, 2006 | _o__) | Ben Finney -- You receive

Re: Requiring GitHub login for actions on Trac

stick to possibilities, truth isn't.” —Mark Twain, | _o__) _Following the Equator_ | Ben Finney -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop r

Re: Requiring GitHub login for actions on Trac

neat, and wrong.” —Henry L. Mencken | _o__) | Ben Finney -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and sto

Re: Requiring GitHub login for actions on Trac

nue. I also don't want these two issues to be tied together. -- \ “Facts are stubborn things; and whatever may be our wishes, our | `\ inclinations, or the dictates of our passion, they cannot alter | _o__)the state of facts and evidence.” —John Adams, 1770-12-04 | Ben Finney

Re: Requiring GitHub login for actions on Trac

swim without getting wet?” —Steven | `\Wright | _o__) | Ben Finney -- You received this message because you are subscribed to the Google Groups "Django developers" g

Re: Requiring GitHub login for actions on Trac

at there are fairies at the bottom of it | _o__) too?” —Douglas Adams | Ben Finney -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-devel

Current check for explicit app_label will cause a lot of headaches

In stable/1.7.x, I'm getting a lot of these warnings: venv/src/django/django/contrib/sites/models.py:65: RemovedInDjango19Warning: Model class django.contrib.sites.models.Site doesn't declare an explicit app_label and either isn't in an application in INSTALLED_APPS or else was imported before

Re: Featurereuqest: Helpfull tracebacks

Florian Apolloner writes: > On Thursday, August 22, 2013 6:43:39 AM UTC+2, Ben Finney wrote: > > > > This could be done by having Django's database interface catch the > > error, and chain a new exception from that one: > > Knowing the model alone is imo pr

Re: Featurereuqest: Helpfull tracebacks

need the forgiveness of God, but of each | _o__)other and of ourselves.” —Robert G. Ingersoll | Ben Finney -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receivi

Relative path support for TEMPLATE_DIRS and others in settings.py (django ticket 694)

50632/favorite-django-tips-features). This is a workaround, not a solution. I would like to see support for relative paths. It seems the solution is simple, but I wonder if there is some compelling reason to require absolute paths? - Ben -- You received this message because you are subscrib

Re: #3011 - Custom User Models -- Call for final review

On Tuesday, September 18, 2012 9:34:38 PM UTC-4, dstufft wrote: > > On Tuesday, September 18, 2012 at 9:13 PM, Ben Slavin wrote: > > Lastly, I haven't seen a path to easily allow third-party apps to > gracefully support both The Old Way and The New Way (1.4 and 1.5). It feels

Re: #3011 - Custom User Models -- Call for final review

p;& ./manage.py migrate fake) To be clear, the majority of this burden lies outside of Django (at least until we merge the migration branch). I tried to start the dialogue with the South community today, but I think we're well advised to make sure that community is aware of the issues th

Re: #3011 - Custom User Models -- Call for final review

and to everyone who's been part of forming this solution over the last six years! Best, - Ben -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-deve

Re: extra files in startproject

especially not in parallel to the OS which often has its own package manager. -- \ “For fast acting relief, try slowing down.” —Jane Wagner, via | `\ Lily Tomlin | _o__)

.save_m2m() failing with multi-database error

27;t see anything implying that this wouldn't work. I suspect the unusual thing I'm doing is creating instances of a Django model within my field's to_python() method. Most of the existing fields use to_python() to cast to datetime or Decimal. Is it not possible to convert value

Re: Advice on #13260 - '%' in args to urlresolvers.reverse()

omatically, the other saying it's up to the user. Cheers, Ben -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send em

Re: Re-open #7231: New "join" parameter for the "extra" QuerySet method

Even if it is a kludge, it still accomplishes something that .raw() cannot (as Dan put forth). I think deprecating it in favor of raw doesn't make much sense, since they are two different things. On Mar 9, 2011 4:06 PM, "Dan Watson" wrote: > > > On Tuesday, March 8, 2011 6:16:26 PM UTC-5, Russell

GSoC 2011 student contribution

Hello Django developer community, my name is Ben Ripkens and I'm planning to contribute to the Django project through this years Google Summer of Code. I found the ideas page for 2011 [1] and even though it seems not publicly available I'm curious whether the mentioned ideas are

Re: #6735 -- Class based generic views: call for comment

but there's probably some stuff in there that isn't thoroughly tested. 2) Support for ModelForms isn't quite the same as our current generic views. For edit views, you can specify a model and the form is optional. Ben On 5 Oct 2010, at 15:43, Jacob Kaplan-Moss wrote: > On Tue,

Re: #6735 -- Class based generic views: call for comment

t coverage probably isn't great. Everything seems to work when I've used it in applications, but there's probably some stuff in there that isn't thoroughly tested. 2) Support for ModelForms isn't quite the same as our current generic views. For edit views, you can specify a m

Re: #6735 -- Class based generic views: call for comment

iki page: http://code.djangoproject.com/wiki/ClassBasedViews Ben On 1 Oct 2010, at 12:25, Andrew Godwin wrote: > On 01/10/10 11:17, Luke Plant wrote: >> Passing things around between '_common' and GET and POST makes a simple >> view much more complex than it needs to be, especially when you

Re: Class based generic views in 1.3?

ric views more readable and it will help users' make their views > cleaner. My fork is at http://github.com/daonb/django-class-based-views The request is passed round so methods look like views to decorators. Magically dropping it for decorators seems a bit scary. :/ Ben -- You received thi

Re: Class based generic views in 1.3?

On 3 Jun 2010, at 17:45, Carl Meyer wrote: > On Jun 2, 6:20 pm, Ben Firshman wrote: >> Yeah, this idea came up at the sprints, but it's a little too magic for my >> tastes. > > I dunno... is __new__ really more magic than having a __call__ method > that magically

Re: Class based generic views in 1.3?

SomeClass is defined as a > class, then x will be an instance of SomeClass. Yeah, this idea came up at the sprints, but it's a little too magic for my tastes. Ben -- You received this message because you are subscribed to the Google Groups "Django developers" group. T

Re: Class based generic views in 1.3?

r problems. No boilerplate, and it's really hard to make it unsafe thread-wise. An example of how it could work: http://github.com/bfirsh/django-class-based-views/blob/master/class_based_views/base.py Thanks Ben On 29 May 2010, at 00:07, Luke Plant wrote: > On Friday 28 May 2010 15:51:32

Re: Class based generic views in 1.3?

e view by raising an exception if a View instance is called twice. Of course, people who understand the threading issues are free to create their own class-based views. I like this method because of its transparency. I fear having to explain as_view() in the documentation. Thread problems are hard to

Re: Class based generic views in 1.3?

> dropped from 1.2", so in all likelihood, yes. However, that doesn't > mean that they will definitely be in 1.3 - someone still needs to do > the implementation. If you really want class based generic views, be > like Ben and make it happen -- show us the code!. Oooh, clas

Advice on #13260 - '%' in args to urlresolvers.reverse()

onsidered a bug, then urlquote should be applied to all items in args and kwargs for reverse. That would mean that this test is wrong though: >>> reverse('special', args=[r'+\$*']) '/special_chars/+%5C$*/' It would have to output: '/special_chars/%2B%5C%24%2A/' Cheers, Ben signature.asc Description: This is a digitally signed message part

Re: 1.2 beta?

On 27 Jan 2010, at 22:50, Ben Firshman wrote: > > On 27 Jan 2010, at 15:36, Russell Keith-Magee wrote: >> >> However, my initial impression: one way to dramatically increase your >> chances is to make sure the patch applies to trunk, and passes all the >> test

Re: 1.2 beta?

nt patch on the ticket, I currently get 4 patch failures. Once I > fix those the way I suspect they are meant to be fixed, I get a failed > test case (SyndicationFeedTest.test_add_domain). Oh gosh, sorry, I thought I fixed all those problems. I'll get it fixed against trunk this evening.

Re: 1.2 beta?

lock things down? I suppose it's too late for #12403 isn't it? http://code.djangoproject.com/ticket/12403 Ben -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develo

Re: Feedback: Syndication feed views

Is it too late to sneak this in in as a minor feature? I have some time now, so I can write up some more documentation if it's needed. Ben On 4 Jan 2010, at 13:07, Ben Firshman wrote: > Is there any more documentation that I should write before the feature > freeze tomorrow?

Re: Model validation incompatibility with existing Django idioms

-Original Message- From: Ivan Sagalaev Date: Sun, 10 Jan 2010 03:25:29 To: Subject: Re: Model validation incompatibility with existing Django idioms Joseph Kocherhans wrote: > # Run validation that was missed by the form. > p.validate_fields(fields=['user', 'pr

Re: idea for using RequestContext by default

traceback because pretty debug pages aren't shown for exceptions raised in middleware. Is there any reason why exceptions in middleware aren't handled? Ben -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to th

Re: Feedback: Syndication feed views

Is there any more documentation that I should write before the feature freeze tomorrow? Thanks, Ben On 22 Dec 2009, at 00:39, Ben Firshman wrote: > > On 21 Dec 2009, at 20:06, Luke Plant wrote: >>> I've documented it in some detail in the release notes. Is this &g

Add querystring helper methods to Page class

A ticket has already been created for this, but SmileyChris recommended I bring the issue up here. Working with pagination and query strings within a template can be painful. Personally, I have never had a situation when I was paginating using a GET parameter where there were not other parameters

Re: Feedback: Syndication feed views

to before, or a caveat like > "if you are only using the high level feed framework (the feed() > view)" or something. > I've gone a little further than that in the patch I've just put on the ticket (1), but this probably needs documenting in more detail. Thanks

Re: Feedback: Syndication feed views

On 21 Dec 2009, at 12:29, Luke Plant wrote: > On Sunday 20 December 2009 13:04:00 Ben Firshman wrote: >> Okay, I've updated the ticket with a new patch: >> >> http://code.djangoproject.com/ticket/12403 >> >> I wasn't sure on the extent of the depre

Re: Feedback: Syndication feed views

Okay, I've updated the ticket with a new patch: http://code.djangoproject.com/ticket/12403 I wasn't sure on the extent of the depreciation warnings required, but hopefully that's the sort of thing needed. Thanks, Ben On 20 Dec 2009, at 12:15, Ben Firshman wrote: > Oops,

Re: Feedback: Syndication feed views

Oops, looks like I used the wrong git diff command and it didn't include any new files. I'll have a stab at the depreciation warnings too. Ben On 20 Dec 2009, at 02:49, Jacob Kaplan-Moss wrote: > On Sat, Dec 19, 2009 at 8:33 AM, Jacob Kaplan-Moss wrote: >> Code-wise, thoug

Re: Feedback: Syndication feed views

Patch and ticket done. Any comments? http://code.djangoproject.com/ticket/12403 Thanks, Ben On 17 Dec 2009, at 10:06, Ben Firshman wrote: > I've made a few more changes, added many more tests and written > documentation. This now fixes #6188, #6304, #6618, #6969, #8758, >

Re: Feedback: Syndication feed views

e. Thanks, Ben On 28 Nov 2009, at 15:43, Ben Firshman wrote: > Hi all, > > I originally had great plans for refactoring the syndication contrib > app, but a lack of time and the thorny issue of backwards > compatibility has forced me to stick to the one big feature: making

Feedback: Syndication feed views

Django's documentation is on its way. This currently fixes tickets #6188, #6304, #6969, #8758, #8989 and #11069. I plan to fix the trivial tickets #6618, #7039, #7936, #10334, #11939 and #11973 before it's ready for committing. Ben -- You received this message because you are sub

Re: Oracle/GIS Testers Needed

want to hijack you branch specific stuff any further)? Cheers, Ben On Nov 20, 4:06 pm, Alex Gaynor wrote: > On Fri, Nov 20, 2009 at 11:03 AM, ben wrote: > > Hi Alex, > > > I have oracle at work with all versions from 9i to 11. I'd be happy to > > run the tests on

Re: Oracle/GIS Testers Needed

ould you mind fixing it? Cheers, Ben On Nov 20, 3:17 pm, Alex Gaynor wrote: > On Fri, Nov 20, 2009 at 8:26 AM, Karen Tracey wrote: > > On Fri, Nov 20, 2009 at 1:14 AM, Alex Gaynor wrote: > > >> Hey all, > > >> Russ and I have been working on getting the multi-db

Re: Transactions

Isn't it TRANSACTION_MANAGE = True? Ben On 2 Nov, 17:19, Jacob Kaplan-Moss wrote: > On Mon, Nov 2, 2009 at 11:27 AM, Ben Ford wrote: > > I'm really curious though -- can anyone remember far back enough to > > know where this came from? I haven't been able t

Transactions

ne remember far back enough to know where this came from? I haven't been able to find a single mention of DISABLE_TRANSACTION_MANAGEMENT anywhere in django's history! Cheers, Ben P.S. I'm fully aware that the way our app is working is causing our problems, and that it should probabl

Re: Buildbot failure

If buildbot is failing for you could I suggest hudson? Yeah i know it's java - but I've been using it for python CI for the last few months and it's been great. It's a snap to set up, (especially with buildout) and the unittest tracking over time is really good too. Ben 200

Re: Change list default sort modification proposal

he level of complexity you are > introducing. There is always a strong inclination in the the project for > simplicity. > > > On Thu, Sep 17, 2009 at 5:42 PM, Ben Davis wrote: > >> I'm not sure if anyone's seen this, but I've written a patch for >> multi-sort co

Re: patch for # 7270, select_related cannot follow reverse one-to-one relationship

fair game to re-assign this (or mark it as unassigned so that someone else can pick it up)? I don't want to step on anyone's feet... On Fri, Sep 4, 2009 at 7:09 AM, Russell Keith-Magee wrote: > > On Fri, Sep 4, 2009 at 6:30 AM, Ben Davis wrote: > > Hi I've submitted

Re: Change list default sort modification proposal

I'm not sure if anyone's seen this, but I've written a patch for multi-sort columns in the changelist ui here: http://code.djangoproject.com/ticket/11868 Not sure if this is what you guys had in mind, but I'd be interested in your feedback. On Thu, Sep 17, 2009 at 12:57 PM, Joshua Russo wrote:

Re: Question on ticket triage process

So by documentation, do you mean updating the official django docs, or better documentation in the code itself? On Sat, Sep 12, 2009 at 2:15 PM, Eric Holscher wrote: > At first glance, tests and documentation. Everything needs both of these > things before they go into trunk. Having a complete

Question on ticket triage process

I noticed that ticket #9015 has been sitting at "accepted" for almost a year now. What's the next step for such a ticket? Does it need a milestone? Also, who is responsible for setting milestones? --~--~-~--~~~---~--~~

#11868, UI proposal for sorting by multiple fields in changelist

http://code.djangoproject.com/ticket/11868 I've made an attempt at adding multiple sort columns to the admin changelist. I'm basically putting this up here as an initial proposal of what I think would be a good starting point for a UI for multiple column sorting. The idea is that each time you c

patch for # 7270, select_related cannot follow reverse one-to-one relationship

Hi I've submitted a patch for this bug that I'd like to have considered for some trunk action... I can't take the credit for all the work on this, but it seems I'm taking the initiative to get it resolved. I really only had one question about a particular change that was needed in order for the

Re: Feeds as views.

There's no elegant way to add custom elements/attributes to the feed. It is possible using the lower level feedgenerator, but it's not elegant by any means. I'll have a think about it... Ben --~--~-~--~~~---~--~~ You received this message bec

Re: Feeds as views.

On 3 Aug 2009, at 14:50, Alex Gaynor wrote: > > Ben Firshman has written similar code that is backwards compatible > with the current implementation: > http://github.com/bfirsh/syndication-view/tree/master > > Alex I started going through all the syndication tickets and

Re: django doc improvement suggestion

Hi guys, I raised a ticket about doc improvements too: http://code.djangoproject.com/ticket/11152. I'm also happy to provide patches to make django's docs play nice with others. Ben 2009/7/6 Russell Keith-Magee > > On Sun, Jul 5, 2009 at 4:47 PM, Amit Upadhyay wrote:

Re: [gsoc2009-testing] Windmill Runners Kicking it up a Notch

ading data to test. Cheers, Ben 2009/6/27 Kevin Kubasik > So, up until now, most of the work on windmill hasn't exactly been 'tester > ready' in that, if you didn't you my exact incantation of settings, luck, > module versions and love, you didn't get very f

Re: Denormalisation Magic, Round Two

re I am. Love what you're doing, Ben. On Sun, Nov 30, 2008 at 3:33 PM, Christian Schilling < initcr...@googlemail.com> wrote: > > On Nov 30, 9:55 pm, Andrew Godwin wrote: > > I have a Trac setup around on my server for South, so if you want I'll > > kick th

Re: Feeds refactoring

but got delayed in the interest of the schedule. > * Named URLs for feeds > * Deploying at arbitrary URLs, rather than /feed/// > * Member per-feed permissions 2nd and 3rd issues are fixed, 4th is straight forward. At the moment I'm

Re: Feeds as views.

definitely makes sense. http://github.com/bfirsh/syndication-view/tree/master I took the backwards incompatible approach, with the intention of writing a separate Feed class that hacked in the old methods for backwards compatibility. Ben --~--~-~--~~~---~--~--

Re: Search for the ORM and Haystack

's no straight forward way of searching over multiple models. It could be done with another generic "document" model updated by signals, but this depends entirely on what fields you want to search over or filter by, so is quite site specific. I suppose some sort of magic ab

Search for the ORM and Haystack

ternal search engines for Django, I would encourage you to get involved! http://groups.google.com/group/django-haystack/ I will be at EuroDjangocon, so maybe we should hold a discussion of some sort if anyone is interested. Search is an area that has been disorganised for a while; new user

Re: Model validation

Hi Honza, Would this code be an approach I could take with my work on fixture? (See my message from a couple of days ago). Cheers, Ben 2009/3/10 Honza Král > > Hi, > The code on github works (tests pass) but is not ready for production > use. What you can do to help is test and m

Re: Declarative fixtures for django

: facing only in the direction of > upstream dependencies. But if you can make it worth both ways, why not? Yep, this would be quite a nice aim, if an upstream app already had tests and was using fixture, then you could use those fixtures to provide the data where your models are referring to

Declarative fixtures for django

last_name = "Herbert" class guido: first_name = "Guido" last_name = "Van rossum" class app__Book(DataSet): class dune: title = "Dune" author = app__Author.frank_herbert class python: title = 'Pyt

Re: Silently capturing all UnicodeDecodeError exceptions in widget rendering

output when DEBUG=True so that you could throw it into your templates without having to delete it for deployment. Thoughts? Cheers, Ben --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group

Silently capturing all UnicodeDecodeError exceptions in widget rendering

again, but it certainly wasn't expected behavior. At the very least, maybe we could return 'UnicodeDecodeError' instead of a blank string? Cheers, Ben --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Dja

Re: Custom FilterSpecs #5833 planned for Django 1.1?

n it's really worth. :) Simply having custom filterspecs will be useful regardless of the details of how they are implemented. Thanks to André for updating my patch--I was going to do it, but you beat me too it. Cheers, Ben --~--~-~--~~~---~--~~ You received

Re: Custom FilterSpecs #5833 planned for Django 1.1?

unknown parameters. This seems kind of ugly, but I'll bet there are many frameworks out there that simply ignore unknown parameters. Thoughts? Cheers, Ben --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django develo

Re: Custom FilterSpecs #5833 planned for Django 1.1?

On Feb 7, 12:35 pm, Alex Gaynor wrote: > On Sat, Feb 7, 2009 at 8:27 AM, Ben Gerdemann wrote: > > A couple things, first the patch still has a pair of TODO comments, so > either those comments are no longer applicable, or what they refer to should > be fixed.  Secondly, it needs

Custom FilterSpecs #5833 planned for Django 1.1?

everal months. Is there a way that I can help here? Also, wanted to take this opportunity to thank all the developers. This is my first web project using Django and it's been a joy to work with. :) Cheers, Ben --~--~-~--~~~---~--~~ You received this messa

Re: Dropping Python 2.3 compatibility for Django 1.1

. I also agree it's worth getting a feel for the need for 2.3. I'm sure there's quite a few RHEL <5 boxes out there for example. Ned's suggestion is a cunning one, but a Q on the user list might be a useful first move. Ben On Nov 26, 1:20 am, Julien Phalip <[EMAIL

Re: Python 2.6 abstract base classes

Named tuples looked like good juju in Raymond Hettinger's talk at pyconuk too! not sure if they're in 2.6 or 3.0 though Ben 2008/10/2 Marty Alchin <[EMAIL PROTECTED]> > > Looking over the new things in Python 2.6, I wonder if there are plans > to inherit from any of the

Re: RFC: django.template refactoring (#7806)

I take it that most are aware of: http://lucumr.pocoo.org/cogitations/2008/09/16/why-jinja-is-not-django-and-why-django-should-have-a-look-at-it/ It seems like a very well thought out and thorough write up. Ben 2008/9/17 Johannes Dollinger <[EMAIL PROTECTED]> > > > Woul

Re: multi-delete and edit form+changelist unification

On 9 Sep 2008, at 21:40, Matthias Kestenholz wrote: > > On Mon, Sep 8, 2008 at 6:55 PM, Ben Firshman <[EMAIL PROTECTED]> > wrote: >> >> tusk-cms [0] has a fantastic admin interface for django-mptt based >> around the jQuery nestedSortables widget [1]. I adapt

Re: multi-delete and edit form+changelist unification

rd. If there's interest, I'll write a patch for django-mptt for a generic admin interface. Ben [0] http://code.google.com/p/tusk-cms/ [1] http://www.bernardopadua.com/nestedSortables/test/widget/ --~--~-~--~~~---~--~~ You received this message because

Re: MultiDb status ?

lickr does this.) You could also move the sharding from the application to the db. MySQL has MySQL Proxy <http://forge.mysql.com/wiki/MySQL_Proxy> which HSCALE <http://hscale.org/display/HSCALE/Home> uses. Not sure about other DBs. This way Django would just keep working as is. Ben. -

Sprinting

companies using django in the Oxford area -- Regards, Ben Ford [EMAIL PROTECTED] +447792598685 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send e

Re: Sprinting

ny of those would be good! Ben 2008/7/22 Tom Dyson <[EMAIL PROTECTED]>: > Hi Ben > > Some of us (at Torchbox) would be interested, depending on dates. Are you > planning to coincide it with one of the main Django sprints? > > Cheers > > Tom > > > On 22 Jul 2008

Re: Sprinting

that would obviously help! Cheers, Ben 2008/7/22 Ben Ford <[EMAIL PROTECTED]>: > Hi all, > > Appologies for being a couple of weeks late with this... I'm currently > working for in a team developing a django site and we'd like to offer our > facilities (office space, wir

  1   2   >