I'm in the process of creating a FileBrowseField that inherits from the
CharField, but implements similar accessors to the File/ImageField. e.g.
get_%s_url
Additionally, in the admin, I want it to pop-up a filebrowser to allow
me to select the file I want.
I'm currently using a modified version
On Wed, 2006-09-06 at 17:36 -0500, Marc D.M. wrote:
> I'm in the process of creating a FileBrowseField that inherits from the
> CharField, but implements similar accessors to the File/ImageField. e.g.
> get_%s_url
>
> Additionally, in the admin, I want it to pop-up a filebrow
On Thu, 2006-09-07 at 03:41 +, SmileyChris wrote:
> When moving an app to a different project, I had to go through and fix
> all the references to my project name in code. Is there a better way to
> import my code? Currently I import like:
>
> from projectname.appname.models import Model
>
>
On Wed, 2006-09-06 at 22:49 -0700, Michael Spencer wrote:
> If you're really hunting for speed, there is a significant boost available in
> the common special case of a python function curried with one positional
> argument. In this case, you can [ab]use the method binding machinery, e.g.:
>
>
On Thu, 2006-09-07 at 13:28 -0500, Adrian Holovaty wrote:
> On 9/7/06, Michael Spencer <[EMAIL PROTECTED]> wrote:
> > Martin's version is indeed faster, but has a 'gotcha' in that it precludes
> > passing a keyword arguments named 'fct' to a curried function...
> > [...]
> > Better to rename fct t
On Thu, 2006-09-14 at 02:09 +, Gary Wilson wrote:
> Out of curiosity, any one know for what reason using empty strings for
> CharFields is the Django convention? Technically, isn't an empty
> string still data? Isn't it a bit confusing that some fields get
> default values and others do not
On Tue, 2006-09-12 at 14:35 -0500, Adrian Holovaty wrote:
> The template would look like this:
>
>
> {% if form.sendername.errors
> %}{{ form.sendername.errors.as_ul }}{% endif %}
> Your name: {{ form.sendername.as_text }}
>
> {% if form.senderemail.errors %}{{ form.senderemail.
