implement tests for __str__ method without creating
migrations?
Let me know what you think about it.
Julian
Adam Johnson schrieb am Montag, 2. November 2020 um 10:21:06 UTC+1:
> I don't think we can use just "Relation to" because M2M relationships are
> two-way by default. Wh
… one last thought:
The verbose name could be: “Media Item-Piece relation”
The string presentation could be: “Relation to ”, e.g. “Relation to Piece xyz”
Together:
*Media Item-Piece relation: Relation to Piece xyz (ID: 11773)*
Julian Klotz schrieb am Dienstag, 27. Oktober 2020 um 09:30:59 UTC
people to
the place where they can change this relation.
*My main question is, does this not trigger migrations on user projects?*
Good point. I just checked – interestingly, neither changing the verbose
name nor the __str__ method triggers new migrations 拾
Best regards
Julian
Adam Johnson
.
Here’s what I’ve got so for; it only fixes the model’s verbose name, not
its string presentation.
Best regards
Julian
[…]
to = make_model_tuple(to_model)[1]
from_ = klass._meta.model_name
if isinstance(to_model, str):
to_label = to
to_label_plural = to
else
issues you might have encountered that
would be great to have as a check in the Django core.
And feel free to propose any checks unrelated to URLpatterns, too.
Cheers
Julian
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to D
Hey there,
I have been spending a lot of time working with FormWizard recently and had
a few ideas on where it might be able to be improved. Here are some of my
thoughts, let me know if these are things the community would find
interesting.
1) More seamless navigation between steps of the
e, but it may be a bit trickier than it looks at
> first.
>
> On Wednesday, May 28, 2014 7:06:00 AM UTC-4, Julian Wachholz wrote:
>>
>> Hi django-developers
>>
>> I'd like to propose a relatively small change to the way we configure our
>> SMTP email backends
caches and databases,
so why not for sending email (at least with the SMTP backend).
I've already created a POC branch complete with docs and deprecation
warnings here:
https://github.com/julianwachholz/django/tree/feature/12factor-smtp
Please let me know what you think!
Cheers
Julian
PS
Is there any document available that describes WHAT Django is? I am
not looking for an installation guide, neither for tutorial, nor for
"Django is a high-level Python Web framework". But: What does this
framework include? What is it used for? How does it increase
productivity? Why shouldn't I use
that binary chunk. This would make the base signer class more
useful for applications where encoding is not necessary. And set-
cookie should be robust enough to know when the data passed to it
needs encoding.
-=Julian=-
--
You received this message because you are subscribed to the Google Groups
Some months ago I tried a snippet from djangosnippets.org which shows a
upload progress bar. I think some people want to use snippets like that and
a multi-threaded server would help you developing such applications.
2008/11/16 Vinay Sajip <[EMAIL PROTECTED]>
>
>
>
> On Nov 16, 6:26 am, Chris
Hi there,
writing a statistic-software i do need field lookups like day, year
but more specific: hour, minute, second.
what about those? can i modify my django-app to add them?
regards
julian
--~--~-~--~~~---~--~~
You received this message because you
>
> Ahem ... where's the patch in the ticket? Perhaps I'm being dumb, but I
> honestly don't see one.
>
Okay, sorry, it should have been this link:
http://code.djangoproject.com/ticket/285
but maybe i am totally wrong and better stop writing.
julia
Sorry, i did not want to offend someone, but it was just a lttle bit
frustrating.
there is a patch wich was postet here:
http://code.djangoproject.com/ticket/1516
but it has not been applied to the yet, maybe i will do it manually
with my own local django-installation.
kind regards
julian
in a typically situation
(django-application in a subfolder with fastcgi) and isn't very well
documented (not even a little comment in the docs).
please tell me why noone has it fixed yet and when do you plan to do?
regards
julian
--~--~-~--~~~---~--~~
You received
(i.e. RSS/ATOM, web services and the
like).
--
Julian 'Julik' Tarkhanov
please send all personal mail to [EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
T
On Jan 27, 2007, at 6:44 PM, ak wrote:
> And another thing I still don't understand is: let's pretend I use
> MySQL 4.0 with national charset and my templates are in the same
> charset too. How would work:
It should not work.
--
Julian 'Julik' Tarkhanov
please send all personal m
On Jan 27, 2007, at 6:44 PM, ak wrote:
> 1. newforms are with unicode inside
> 2. ORM is with str inside
3. welcome to the world of pain
--
Julian 'Julik' Tarkhanov
please send all personal mail to
me at julik.nl
--~--~-~--~~~---~--~~
You re
d to stay liberal
in 952 - primarily because
it's still unknown how Django authors want to approach this.
--
Julian 'Julik' Tarkhanov
please send all personal mail to
me at julik.nl
--~--~-~--~~~---~--~~
You received this message because you are subscribed to t
On Jan 26, 2007, at 2:25 PM, Gábor Farkas wrote:
>
> Julian 'Julik' Tarkhanov wrote:
>>
>>
>> Python's unicode is actually UTF-16
>
> on linux it's usually utf-32, and on windows it's usually (always?)
> utf-16.
sorry I forgot that - it's been a year at le
every database driver has to be scrutinized
for whether it returns unicode strings proper.
I know, it seems so nice to be liberal and allow people to choose
their encoding but just too many situations prove that to be the
Wrong Choice.
--
Julian 'Julik' Tarkhanov
please send all persona
On 7-jul-2006, at 17:50, Bill de hÓra wrote:
> This is my point. Cut what exactly? "No good" for what exactly? We
> could file patches to see what sticks, but it might be better to
> figure
> what's wanted first, instead of playing fetch me a rock.
This is handled by Unicode standard and is
On 2-jun-2006, at 22:14, Carlo C8E Miron wrote:
>
> On 6/2/06, Julian 'Julik' Tarkhanov <[EMAIL PROTECTED]>
> wrote:
>>
>> I would advise all respected Django contributors to follow the path
>> mentioned here:
>>
>> http://blade.nagaokau
On 2-jun-2006, at 22:14, Carlo C8E Miron wrote:
>
> On 6/2/06, Julian 'Julik' Tarkhanov <[EMAIL PROTECTED]>
> wrote:
>>
>> I would advise all respected Django contributors to follow the path
>> mentioned here:
>>
>> http://blade.nagaokau
I would advise all respected Django contributors to follow the path
mentioned here:
http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/138966
On 25-mei-2006, at 18:27, lazaridis_com wrote:
>
> For a long term project, I am selecting a python based persistency
> system:
http://code.djangoproject.com/ticket/952
On 22-mrt-2006, at 6:54, ak wrote:
>
> Thanks, posted: http://code.djangoproject.com/ticket/1528
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
I file a much broader patch for thus about a few months ago. Check
out the tickets.
On 22-mrt-2006, at 6:54, ak wrote:
>
> Thanks, posted: http://code.djangoproject.com/ticket/1528
--~--~-~--~~~---~--~~
You received this message because you are subscribed to
27 matches
Mail list logo
