Hello,
The most beautiful way (IMHO) is to create a widget type for this. See this
answer on SO[1]. I wonder why this is not part of Django yet…
[1] http://stackoverflow.com/a/5155576/1305139
On 25 Sep 2015 01:53, "eli" wrote:
> Hi Guys,
> A noob here,
>
> I have two models,
>
> class Students(
Hi Guys,
A noob here,
I have two models,
class Students(CommonInfo):
first_name = models.CharField(max_length=75)
surname = models.CharField(max_length=75)
class_score = models.ForeignKey(Course, related_name='course')
exam_score = models.ForeignKey('House')
Thanks Ryan. That's an interesting additional consideration. I don't think
we're particularly married to Django admin as an open interface to the
database where I work, although I can see how that wouldn't always be the
case. Also, I think Luis's suggestion could help to quell the resistance
yo
http://oscarcommerce.com/
or https://www.djangopackages.com/grids/g/ecommerce/
2015-09-24 13:42 GMT-06:00 Paul Savignano :
> Hi Django-users,
> I am somewhat new to Django and have a client interested in an online
> store/e-commerce for their foodservice operation.
> Are there any tutorials you
Hi Felix,
>From what I know model and form DateField are completely TIME_ZONE
agnostics.
This is not the case for DateTimeField however. Is this what you're using?
Simon
Le jeudi 24 septembre 2015 15:13:01 UTC-4, felix a écrit :
>
> El 23/09/15 17:12, felix escribió:
>
>
> When today's date is
Hi Django-users,
I am somewhat new to Django and have a client interested in an online
store/e-commerce for their foodservice operation.
Are there any tutorials you can recommend on this subject?
Thanks in advance for any help you may offer!
*Paul*
--
You received this message because you are
It really depends on the project you're working on. The resistance comes
mostly from developers who utilize the admin as an open interface to the
database with minimal restrictions. I like to use the admin this way for
large projects that are used by many people, building out a custom "staff"
p
El 23/09/15 17:12, felix escribió:
When today's date is entered in the form it shows a form error saying
that this date (today) is in the future.
What is wrong with the validator I'm using to allow dates until today?
models.py
...
import datetime
...
class SolicitudBase(models.Model):
Dear Luis, I got it. Thank you so much.
On Thu, Sep 24, 2015 at 1:05 AM, Luis Zárate wrote:
> As Remco said your problem are with your pattern because starts with $ or
> have ^*$*
>
>
>
> [projectname]/
> ├── [projectname]/
> │ ├── __init__.py
> │ ├── settings.py
> │ ├── urls.py <--
This plugin won't work with Jinja2 templates, but another coverage.py
plugin could be written for Jinja2, sure. Get in touch if you want to
get started on it.
--Ned.
On 9/20/15 9:45 AM, Avraham Serour wrote:
would this work with jinja2 templates also?
On Tue, Aug 25, 2015 at 3:45 AM, Ned Ba
I am upgrade from Django v 1.6 to v1.8. I use this code:
query_set = Rubrica.objects.filter(...).annotate(count=Count('..')).order_by
('user', '-pub_date')
query_set.query.group_by = ['user_id']
On Django version 1.6 this is works fine, but on version 1.8 results is not
grouped by user_id field.
I am upgrade from Django v 1.6 to v1.8. I use this code:
query_set = Rubrica.objects.filter(...).annotate(count=Count('..')).order_by
('user', '-pub_date') query_set.query.group_by = ['user_id']
On Django version 1.6 this is works fine, but on version 1.8 results is not
grouped by user_id field
Hello,
I have an issue with the admin and inlines for related models. When hitting
save on a model editing page I get this traceback:
Traceback (most recent call last):
File "lib/python2.7/site-packages/django/core/handlers/base.py", line 132, in
get_response
response = wrapped_callback(r
Hello all genius developers of django, I am a fresh user of django and I
don't know how can I display data from django by input text form in html.
Here is my javascript code, I want to display data by value inputted in
input text form.
function date(ele){
if(even
> I'm baffled by the fact that the __str__ method of an instance fails
> before the instance is saved but works fine afterwards.
>
> The relevant snippet from my models.py file:
> class Journal(models.Model):
> date = models.DateTimeField(default=timezone.now)
Check the docs on the use of 'def
15 matches
Mail list logo
