Before voting for more magic to the transaction middleware, I'd vote
to remove it altogether. Explicit is surely better than implicit in
this case. The admin already uses commit_on_success, etc.
On Oct 18, 1:22 pm, David Winterbottom
wrote:
> The current implementation of django.middleware.Transa
It's quite a common practice to customize a model's delete method.
This normally leads to the recommended practice of "just loop through
instances and delete each in lieu of using QuerySet.delete". That
works well, within limited context. However, when you've got a model
that's high up in the food
My "table" typo was intended to be the "restaurant" of a Table model
(it's late :)
--
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
Adrian,
My apologies, what I'm meaning is: on deletion of the restaurant,
rather than issuing a bulk SQL deletion of the Table instances, call
the delete method for each.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this grou
Did my last post answer the question you had, Adrian?
--
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 email to
django-developers+
> Or is your main objection having to branch against the specific
Simply put, there should be an *optional* way to ensure a model's
*explicitly* defined delete behavior is honored without having to
write hacks, signals, and/or patches of any kind (ie, make it DRY, and
therefore less error-prone).
On Dec 4, 10:46 pm, Justin Holmes wrote:
> "hacks, signals, and/or patches"
>
> One of these things is not like the other
While I agree that signals allow for neat decoupling, they aren't as
DRY or quick as a simple field kwarg. Imagine you have 8 models that
have custom delete methods. Which i
be willing to work in that direction.
On Dec 5, 8:58 am, Carl Meyer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 12/05/2011 08:31 AM, Yo-Yo Ma wrote:
>
> > While I agree that signals allow for neat decoupling, they aren't as
> > DRY or quick a
Take the following models:
class Person(models.Model):
name = models.CharField(_('Person'), max_length=255)
class Production(models.Model):
person = models.ForeignKey(Person)
title = models.CharField(_('Title'), max_length=255)
class Meta:
unique_together = (('person', 't
Re Russell: Pertaining to autocommit, I wrapped the view (my base
view's dispatch method) in commit_on_success. I asked here (as opposed
to opening a ticket) because I wasn't certain there was a way to fix
this, but it just seemed too wrong to not at least bring to the table.
After Karen's reply I'
While graceful degredation is important, it isn't something that a web
framework should provide. It is something that you, the web
application developer, should provide. Simply code your web pages to
function reasonably without JavaScript. Then, use JS to add the bells
and whistles. I can't speak f
Is this a prank, or is there really going to need to be a u('') for
every u'' (of which there are thousands, since everything is Unicode
in Django) in my Django apps, in order to use P3K? Removing the "u" is
one thing, but adding another text function seems absurd, no?
name = models.CharField(_(u(
Speaking with regards to the ORM method documented at
https://docs.djangoproject.com/en/dev/ref/models/querysets/#prefetch-related
Of course, ``prefetch_related`` uses a Pythonic join to attach reverse-
related objects and avoids the N+1 queries problem, which of course is
great. However, if you u
If you call ``QuerySet.update`` on the following model, you'll get the
results that proceed it:
# models.py
class Person(models.Model):
cool = models.BooleanField(default=False)
updated_on=DateTimeField(auto_now=True)
# django-admin.py shell
>>> from myapp.models import Person
>>>
>>> #
On a related note, the new timezone.now() functionality is used for
``DateTimeField.pre_save`` when ``auto_now=True``, but it isn't used
for ``DateField.pre_save`` or ``TimeField.pre_save``. Is this a bug I
should report, or is there something I'm missing (I'm pretty
uninformed when it comes to UTC
It seems my previous question was co-opted... by myself, so rather
than try to distract the conversation about TZ stuff (which seems to
be pretty important stuff, esp with the 1.4 launch), I figured I'd
start a new thread with my original question. Here it is:
If you call ``QuerySet.update`` on t
I haven't quite read up on all the UTC-related stuff in Django as of
yet (couldn't find much info about it), but I found some of the posts
above concerning. It would seem that if a DateTimeField should be
updated with ``timezone.now()``, then a DateField should be updated
with ``timezone.now().toda
I actually know so little that I was even more confused by my own
question, but I appreciate your reply, Danny. I feel pretty challenged
when I try to understand timezone-related stuff. Is this correct:
When using UTC, which, if any, are true:
A) If I have a view that simply adds a record of a mo
Thanks, Danny. That's really helpful to me, and I appreciate you
taking the time to explain it.
--
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 thi
I have trunk installed from last night, and this is actual terminal
output (except for the stuff omitted on the left of the $):
(my_venv) myusername$ django-admin.py startproject foobarz
(my_venv) myusername$ ls foobarz/
__init__.py foobarz manage.py settings.py urls.py
(my_v
es for the venv, I show Django-1.4b1-py2.7.egg-
info
On Feb 20, 8:56 pm, Carl Meyer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 02/20/2012 08:31 PM, Yo-Yo Ma wrote:
>
> > I have trunk installed from last night, and this is actual terminal
> >
Thanks, Carl. To fix this issue, I had to delete my local git clone of
the django repo, and then clone the github mirror again before
reinstalling. I thought it was due to the /build in the repo, but for
some reason a ``reset --hard`` didn't even fix it, so I'm not sure how
a rm -r then re-cloning
I'm -1 on this for s specific reason; If you need multiple lines for a
tag, you're doing it wrong.
>>> import this
--
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
After Ned's message, I'm -0, because while I'm not fond of multi-line
tags, I cannot offer a good alternative when it comes to multi-line
"with" tags.
On Feb 25, 6:48 pm, Ned Batchelder wrote:
> On 2/24/2012 11:55 PM, Yo-Yo Ma wrote:> I'm -1 on this for s spec
django/db/models/fields/__init__.py:808: RuntimeWarning: DateTimeField
received a naive datetime (2012-01-01 00:00:00) while time zone support is
active.
The above warning is caused by a JSON fixture having "2012-01-01 00:00:00"
for a DateTimeField timestamp.
Does this mean that fixture loadin
On Mar 25, 2:41 am, Roy McElmurry IV wrote:
> Okay, I have created a Google Doc of my proposal. I have greatly
> elaborated on the idea. I have enabled commenting for anyone with the
> link. Please take a look and let me know either in this forum or in
> the Google Doc if there is anything I can a
Regarding
https://docs.djangoproject.com/en/dev/ref/utils/#django.utils.timezone.override
# views.py
class TZView(DetailView):
def dispatch(self, request, *args, **kwargs):
with timezone.override(est_tz): # Assuming your default
timezone is US/Pacific
return super(TZView
I'd like to suggest adding the ability to connect signals with models
by app label and model name.
Example API:
post_save.connect(
my_signal_handler,
sender='my_app.MyModel'
)
This would allow for better decoupling of code, as well as a far
cleaner dependency graph.
I'm not certain how
I'd be willing to implement this, with some guidance.
--
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 email to
django-developers+
els from app A
inside of app B without having to worry about import order or errors,
due to some crisscross in app A's dependency graph.
On May 12, 4:24 am, Dougal Matthews wrote:
> On 9 May 2012 22:14, Yo-Yo Ma wrote:
>
> > This would allow for better decoupling of code, as well
A request to:
http://www.example.com:8080//foo-bar-baz.html
leads to request.build_absolute_uri() returning:
http://foo-bar.html
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develope
; reporting this here, rather than on the ticket tracker?
>
> Yours,
> Russ Magee %-)
>
>
>
>
>
>
>
> On Mon, May 14, 2012 at 9:55 AM, Yo-Yo Ma wrote:
> > A request to:
>
> > http://www.example.com:8080//foo-bar-baz.html
>
> > lead
, rather than on the ticket tracker?
>
> Yours,
> Russ Magee %-)
>
>
>
>
>
>
>
> On Mon, May 14, 2012 at 9:55 AM, Yo-Yo Ma wrote:
> > A request to:
>
> > http://www.example.com:8080//foo-bar-baz.html
>
> > leads to request.build_absolute_uri() re
Thanks Aymeric, I've reopened the ticket. I skipped the triage page,
thinking it would be about the rules for prioritizing bugs.
On May 15, 3:44 pm, Aymeric Augustin
wrote:
> Hello,
>
> On 15 mai 2012, at 21:36, Yo-Yo Ma wrote:
>
> > I've attached a diff in the tick
I'll start with an example:
Using Jinja2, I can create an environment which is pretty secure (no access
to anything but built-ins and objects explicitly marked "safe"), and
provide a loader who's templates are loaded from the database (e.g.,
``request.client.template_set.all()``), and customize
At:
https://docs.djangoproject.com/en/dev/ref/models/fields/#django.db.models.FileField.upload_to
The docs make mention of the "url" attribute being MEDIA_ROOT + upload_to. I
think whoever wrote it meant that the aforementioned is how the file name/path
is determined, and that also MEDIA_URL +
Is there anyone else out there who doesn't like having to import models from
app X into app Y just so that app Y can connect post save signals to them?
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visi
The following gist demonstrates a strange phenomenon, which occurs when I
use ``python manage.py shell``, but not when I use ``ipython`` alone.
https://gist.github.com/f8c2fd97647de90d915a
I'm not certain whether this is a known issue, or whether it's even a
Django bug, but certainly nothing of
Another good reason for model loading at startup is a good idea; without it,
models.get_models becomes a lie.
--
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-
This may be the intended behavior, but I couldn't find docs on it. My
recommendation would defer to "The Zen of Python"
In the face of ambiguity, refuse the temptation to guess.
I would rather see the typical IntegrityError: Problem installing fixture...
--
You received this message becaus
ptember 24, 2012 5:44:29 AM UTC-4, Aymeric Augustin wrote:
>
> 2012/9/24 Yo-Yo Ma >
>
>> This may be the intended behavior, but I couldn't find docs on it. My
>> recommendation would defer to "The Zen of Python"
>>
>> In the face of ambiguity,
Developer of a pet shop software adds:
feed_before_midnight = models.BooleanField()
because they're planning on carrying baby gremlins... forgets to update the
zoological XML feed importer to use the "feed_before_midnight" value, and
the rest is history :)
On Monday, September 24, 2012 9:21:34
isn't set, ``False`` is implied - only because this seems like the sort of
mini-"bug" that might never warrant fixing due to the ramifications.
On Monday, September 24, 2012 9:18:34 PM UTC-4, Russell Keith-Magee wrote:
>
> On Tue, Sep 25, 2012 at 8:00 AM, Yo-Yo Ma >
>
With ``contrib.sessions`` installed and ``SessionMiddleware`` in use, I
noticed that when Django session cookie is set the ``django_session`` table
is queried on every request, regardless of whether any session data is used
during the request cycle. Making the ``session`` attribute of request a
Why does every conversation about Django's performance met with "GTFO we don't
care"? (that was a rhetorical question :). I'd venture to guess that most "It's
fast enough for me!" responses are predicated on experiences that can be
likened to personal blog development, rather than large scale, 1
I only now realized that this thread had started in a bit of a trolling
fashion, and that there was a similar thread this week. That helps to explain
the slightly more defensive stance.
Django can survive (and thrive) just fine in its current, reasonably performant
state, but performance should
+1
A lot of people are overriding ``save`` and not returning anything, but
this isn't going to hurt them (ideally, they should already be returning
the result of ``super(``, but nobody does).
On Friday, October 12, 2012 9:25:46 AM UTC-4, Chris Wilson wrote:
>
> Hi all,
>
> If the save() method
Problem:
a = A.objects.get(...)
form = AModelForm(data={...}, instance=a)
if form.is_valid():
a = form.save()
else:
a.calculate_foo_field()
a.last_attempt = datetime.now()
a.save() # Oops, now the instance has the bad data provided to the form
Workarounds:
# Get a fresh cop
I'm still working on forming some sort of understanding of what exactly
causes this and/or what is even going on, so any help is much appreciated.
The resultant attached "bars" in the following example:
queryset = Foo.objects.all()
queryset = queryset.prefetch_related('bars__baz')
ob
Hi Anss, thanks for the reply.
The queries are identical.
That's the exact reason I posted. Those two examples should essentially be
the same, save for some sort of operator overloading.
My note at the bottom about providing an empty list instead of the related
cache when calling ``prefetch_r
+1
On Monday, October 29, 2012 5:18:48 AM UTC-4, Jan Bednařík wrote:
>
> There is also related ticket https://code.djangoproject.com/ticket/19141
>
> Jan
>
>
> On Mon, Oct 29, 2012 at 3:36 AM, Matt Austin
> >
> wrote:
> > Hi,
> >
> > Would it be possible to get tags for 1.3.3, 1.3.4, 1.4.2,
This morning read the SQLAlchemy proposal made by Luke Plant in June. I
then decided that this would be a good time to rant about abstraction,
extensibility, and decoupling.
Background
For years, Django has been forced to deal with most implementation issues
from within, inclu
There aren't yet Git tags for the releases.
--
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-developers/-/ipPpizg3flcJ.
To post to this group, send email to dj
Tom,
Create a view that accepts a "uri" argument and returns a 302 to the provided
URI. Then, update your redirect_to callable to urlencode the URI and send them
to /your/redirect/view/?uri=[encoded URI] and problem solved.
--
You received this message because you are subscribed to the Google
-1 FWIW
Computing the root of your project with os.path works just fine and doesn't
require another setting... which, btw, could have no sane default.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web vis
Sorry to be a pest, but will you guys end up adding a Git tag for RC-1?
On Sunday, October 28, 2012 10:38:00 PM UTC-4, Matt Austin wrote:
>
> Hi,
>
> Would it be possible to get tags for 1.3.3, 1.3.4, 1.4.2, and 1.5
> alpha tagged on the github repository? The tagging seems to have
> fallen beh
With all respect, this seems like a bad idea; there would be little, if any,
gain from having this method.
--
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
For anyone developing a SaaS that allows users to create templates through the
UI (e.g., a hosted CMS), separately initializable template system is paramount,
giving the ability to modify multiple settingsin the template system that are
in effect during template rendering, including loaders, tem
A form that has a char field (e.g. "name") when provided a dict of data
will convert the value of "name" to a Unicode, no matter what. I understand
that this is desirable in some circumstances, but it can lead to things
like:
>>> product.name
u"{'haha': 'I am a dict'}"
Perhaps this is desirabl
I should note, the use case for this is when the data is being provided to
the form through a mechanism other than normal HTTP form-encoded via
request.POST, such as an API that consumes JSON.
>>> product.name
> u"{'haha': 'I am a dict'}"
>
>
--
You received this message because you are subscr
The commit
https://github.com/django/django/commit/2f121dfe635b3f497fe1fe03bc8eb97cdf5083b3
fixed a problem where a custom regex validator's customized message was
ignored, in favor of the one set on the class (you just see "Please enter a
valid value").
If I pip install the latest master, th
t that
I install the tip of master and test it out before updating, but that's not
ideal of course.
On Thursday, March 28, 2013 12:34:56 PM UTC-4, Yo-Yo Ma wrote:
>
> The commit
> https://github.com/django/django/commit/2f121dfe635b3f497fe1fe03bc8eb97cdf5083b3fixed
>
Ah, thanks Jacob. Also, great job on the 1.5.1 release. Thanks to everyone
for all the hard work.
On Thursday, March 28, 2013 12:34:56 PM UTC-4, Yo-Yo Ma wrote:
>
> The commit
> https://github.com/django/django/commit/2f121dfe635b3f497fe1fe03bc8eb97cdf5083b3fixed
> a problem wh
A common pattern for larger applications is to maintain bits of reusable
code outside of applications, but still inside of a project (e.g.,
myproject/lib), due to synchronous development and modification of
application and library code. They're parts that aren't really large enough
to warrant t
That's excellent news! Thanks, Carl.
--
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-developers+unsubscr...@googlegroups.com.
To post to this group,
+1, in general.
>> ** The current "myapp." notation is not part of unittest2, and
>> would go away
I don't know of anyone for whom this would represent a breakage in deployment
processes, since it's usually used for quick local testing only.
One concern, however:
How will `django-admin.py te
If you include {{ object.some_datetime }} with the America/New_York
timezone activated in a template and get:
April 10, 2013, 10:00 p.m.
Then, take the same object, timezone, etc., and add the |localize filter -
{{ object.some_datetime|localize }} - you'll get:
April 11, 2013, 2:00 a.m.
It se
The following example can throw a wrench in things, if you don't catch it
right away, since it fails silently.
>>> instance.some_fk_field = unsaved_instance
>>> instance.save()
The following example bit somebody I worked with a couple years back as
well.
>>> instance.some_m2m.add(unsaved_insta
Wow, this is awesome! Thanks so much guys. Too long have I dreamt of the day
when I could include tests for my "lib" and "util", etc. without having to
couple them to one app or another. I'm so excited that this was added so
quickly.
Thanks
Yo-yo
--
You received this message because you are
>
> How about allowing comments only from the patch author and committers?
>
The problem I see with this is that original bug reporters, aside from the
aforementioned groups, are usually the ones most engaged in these comments,
and eliminating them from the process will only serve to further di
There is a fundamental problem here, albeit one that is rooted in simple
misunderstanding.
The burden of proof is on the originator of an idea (i.e., the ticket
reporter). Arguments can be made against the idea in the ticket. Rebuttal
is sent elsewhere. Regardless of the intention, this automat
Using Python 3.4.2 and Django @stable/1.8.x (installed just moments before
this writing), I created a model with a "name" field, then created a
migration for it. Moments after, I added an "age" field to the model,
deleted the 0001_initial.py migration, deleted __pycache__ directories in
my enti
details about what sort of field you added, please?
>>
>> I have seen cases where migrations will create two separate migrations
>> for an initial.
>>
>> --
>> Curtis
>>
>> On 9 February 2015 at 10:11, Yo-Yo Ma
>> > wrote:
>>
>
I was reading through the 1.9 release notes when I came across the new
OPTIONS['libraries'] feature.
Relevant links:
-
https://docs.djangoproject.com/en/dev/releases/1.9/#template-tag-modules-are-imported-when-templates-are-configured
- https://docs.djangoproject.com/en/dev/releases/1.9/#te
CORRECTION:
| Due to #2, you can still run...
Should be:
| Due to #1, you can still run...
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it
Hi Aymeric,
Pardon my misunderstand of the new functionality, and thanks for the
explanation. The ability to use template libraries outside of installed apps
alone is a great addition. Thanks for your hard work on this.
--
You received this message because you are subscribed to the Google Grou
Another reason you want the two to be separate is that you might allow a field
to be blank in forms but then set the value to some context-specific value (vs
a simple default=x) before saving.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Con
To clarify, are you referring to a state where there are validation errors and
the form is redisplayed, whereupon your change the value back to the original
value?
Pertaining the problem you mentioned last (displaying the intermediary result):
you are probably better off using the value from th
I found an N+1 query by inspecting the code of a management command that
was running every 10 minutes, and it made me think, it would be good to
have an option similar to
https://django-debug-toolbar.readthedocs.org/en/1.0/commands.html#debugsqlshell
for management commands in general.
If ther
I may be way off base here, but I actually feel like string_if_invalid should
eventually be removed. It seems like a really bad idea to have a setting that
can muck up an application in unexpected ways. Meanwhile, settings like
DEBUG=True can't muck up your application, even if they're not secur
Today, I decided to check out Django's new password validation
functionality (which is a great feature, btw).
I noticed there was a CommonPasswordValidator, which mentions "1000 common
passwords"...
Part 1.
The first thing that came to mind was, how would one compile a list of 1000
common pas
I just downloaded trunk about 2 hours ago, and I have a template that
has a ’ character (angle style apostrophe that happens if you type
something like "This doesn't work" in Fireworks (turns to "This
doesn’t work" in Abobe Fireworks).
When rendering a static page consisting of only the template,
Perhaps it isn't a bug in Django.
My document's encoding is Western European (CP-1252). Is this
typical, or should I manually choose ASCII?
On Aug 24, 6:35 pm, Yo-Yo Ma wrote:
> I just downloaded trunk about 2 hours ago, and I have a template that
> has a ’ character (angle
rks.
>
> Also, this is more appropriate for the django-users group, django-dev is for
> discussion of development of Django itself, not development of sites that
> use Django.
>
>
>
> On Tue, Aug 24, 2010 at 8:35 PM, Yo-Yo Ma wrote:
> > I just downloaded trunk about 2 hour
ly sure why you're creating templates with it.
>
> On Tue, Aug 24, 2010 at 8:41 PM, Yo-Yo Ma wrote:
> > @Josh - really helpful. Thanks. So, if Django had a bug pertaining to
> > character encoding, it wouldn't be appropriate for me to report it
> &g
Let's say I have a site with 5 sections, 6 main tabs per section, and
7 sub tabs per main tab. In order to display the correct tabs for a
given view, I have to have:
baseform.html
baselist.html
foo_section/form.html
foo_section/list.html
foo_section/spam_sub_section/form.html
foo_s
I'm speaking about something like http://code.google.com/p/django-nav/
One of the main issues I deal with when developing software with
Django is that I need to create a new template for every view that
changes navigation (e.g. tabs). The ability to generate some sort of a
map that allows for sub-
You know what, I thought this hadn't been updated for 3 years because
the downloads section isn't updated. I didn't bother to browse the SVN
for change dates. Thanks Dougal.
Rog
On Aug 26, 10:32 am, Dougal Matthews wrote:
> On 26 August 2010 17:25, Yo-Yo Ma wrote:
>
&
I'm sure this will be met with criticism, but there is a reason why
just about all template languages allow the setting of variables. It
allows you to do things like:
{% for thing in things %}
{{ thing }}
{% if thing.is_the_one %}
{% set_var the_one thing%}
{% endif %}
{% endfo
> statement:http://docs.djangoproject.com/en/dev/ref/templates/builtins/?from=old...
>
> On Fri, Aug 27, 2010 at 10:06 AM, Yo-Yo Ma wrote:
> > I'm sure this will be met with criticism, but there is a reason why
> > just about all template languages allow the setting of
would make me feel better. Thanks a lot for ruining my evil
plans :)
On Aug 26, 6:30 pm, Russell Keith-Magee
wrote:
> On Fri, Aug 27, 2010 at 8:06 AM, Yo-Yo Ma wrote:
> > I'm sure this will be met with criticism, but there is a reason why
> > just about all template languages
I think the thing that would be helpful to most django users is bit
really a navigation helper per se. I think what I need could be solved
with a more generic tool. Russell, tell me what you think about
providing a way to make a view a "child" of another. I'm not speaking
in the CMS sense (e.g. /ac
ee
wrote:
> On Sat, Aug 28, 2010 at 12:32 PM, Yo-Yo Ma wrote:
> > I think the thing that would be helpful to most django users is bit
> > really a navigation helper per se. I think what I need could be solved
> > with a more generic tool.
>
> I don't doubt that
I think it might be a good idea to document the direct usage of the
FileField, and ImageField model fields.
The docs make the assumption that everyone is using ModelForm to
upload files. If I have a file on my hard drive and want to use it to
populate the field, I would try something like:
from
BTW, ignore the PIL imports
On Sep 15, 12:28 pm, Yo-Yo Ma wrote:
> I think it might be a good idea to document the direct usage of the
> FileField, and ImageField model fields.
>
> The docs make the assumption that everyone is using ModelForm to
> upload files. If I have a file o
On Sep 15, 5:52 pm, Russell Keith-Magee
wrote:
> On Thu, Sep 16, 2010 at 2:28 AM, Yo-Yo Ma wrote:
> > I think it might be a good idea to document the direct usage of the
> > FileField, and ImageField model fields.
>
> Sure -- sounds like a reasonable proposal to me. Open a t
Is there any plans to incorporate http://github.com/SmileyChris/easy-thumbnails/
into django.contrib? I have seen so many apps/libraries come into and
go out of existence (http://code.djangoproject.com/wiki/ThumbNails for
instance mentions sorl-thumbnails which is no longer being developed).
I just
P. Novakovic
>
> wrote:
> > I don't want to sound negative, but answering your own question before
> > anyone else can doesn't change the answer ;)
>
> > D
>
> > On Thu, Sep 16, 2010 at 3:00 PM, Yo-Yo Ma wrote:
> >> Is there
ong with the other batteries in the pack.
>
>
>
> On Thu, Sep 16, 2010 at 12:24 PM, Yo-Yo Ma wrote:
> > I have no data to support the following assertion, but it's not too
> > unreasonable: More people probably need thumbnail images than they
> > need comments
tware that satisfies most people's needs for
> > image manipulation within a web development environment, and being in
> > contrib will allow people to use another package if they don't like it.
>
> > On Thu, Sep 16, 2010 at 12:37 PM, Yo-Yo Ma wrote:
>
> >
1 - 100 of 194 matches
Mail list logo
