Hi Chitra,
Django’s contribution guide is here:
https://docs.djangoproject.com/en/1.9/internals/contributing/
That gives you a step-by-step guide to the ways you can contribute, and how
to get started.
If you want some more specific guidelines or mentoring, you’ll need to tell
us a bit more
What performance changes can you expect doing this change? It is probably
that default on MySQL for a good reason.
--
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
+1 for me, too... this aligns with "safe/secure by default".
--
C
On 21/03/16 09:13, Aymeric Augustin wrote:
I agree with Karen.
--
Aymeric.
On 18 Mar 2016, at 22:15, Karen Tracey > wrote:
This is the 2nd major issue I can recall caused by
I agree with Karen.
--
Aymeric.
> On 18 Mar 2016, at 22:15, Karen Tracey wrote:
>
> This is the 2nd major issue I can recall caused by MySQL default of
> REPEATABLE READ transaction isolation level. I think Django should simply
> switch itself to a default of using READ
hi. this a list for django-development discussions. but anyway
for python tutorial [1] see
[1] https://docs.python.org/2/tutorial/
2016-03-20 14:31 GMT-03:00 Chitra Sivakumar :
> Hi ,
>
> I am new to open source and python, I am interested in doing open source
>
On Sunday, March 20, 2016 at 5:57:41 PM UTC+1, Collin Anderson wrote:
>
> Hmm... I suppose the closest alternative we have would be to store the
> base template name in a variable and pass it in from the view.
>
Either way, I fail to see how that feature would be really useful.
--
You received
The client side validation is a very good idea, other frameworks such as
ASP.NET MVC already has some basic client side validation tied to model
fields (equivalent to django forms) and also provides a very easy way to
add custom javascript validation and tie to the model/form.
For the second
Hi ,
I am new to open source and python, I am interested in doing open source
contribution. It will be great !! if some mentor can help me getting
started.
regards
chitra
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django
Hmm... I suppose the closest alternative we have would be to store the base
template name in a variable and pass it in from the view.
On Fri, Mar 18, 2016 at 12:42 PM, Vitaly Bogomolov
wrote:
> Hi, All.
>
> For django.template.backends.django.DjangoTemplates (filesystem and
Hi,
I have been working for preparing a proposal about a new feature for
Django. I'm posting my draft proposal to Gist and want to know my idea is
OK or not. So I can proceed with the right approach. Any suggestions or
advice are welcome.
Abstract of my proposal:
- Automatically generate
Yes, overriding the model field to change the definition of
formfield() works. It is indeed possible to define two model field
classes which have different formfield() methods, for example:
ManyToManyCheckboxField()
ForeignKeyRadioField()
Should Django provide such fields ?
formfield_callback
Hey,
For the past five years, I've been using Django to manage a database of
online applications. I absolutely love it! Makes my job so much easier.
In general, any problems I run into, there's usually an easy workaround.
But I wonder if that's even feasible in this case. Anyway, here's the
I agree with you, generate_filename should just call the field upload_to
and then delegate the whole name generation to the storage.
There's another thing about file storage that is troubling me:
https://github.com/django/django/blob/master/django/core/files/storage.py#L57
The docs state you
Hi, All.
For django.template.backends.django.DjangoTemplates (filesystem and
app_directories) it can be very useful. This can be implemented?
WBR, Vitaly.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
14 matches
Mail list logo