Hi Django developers community
A great greetings
I want share with you the following question:
I have a custom users schema in Django for work with roles or users type,
creating an application named userprofile which will be or will setup my
custom user model.
In my settings.py I have the fol
So as long as I don't use the `params` thing (which I don't) there will be
no problem with my views?
Reading this and the other commit done at the same time, looks like the
function calls behave the way I expect :)
Bernardo
Em domingo, 19 de agosto de 2012 06h44min03s UTC-3, M
y way I find to keep the code compatible with both 1.4 and 1.5
is doing:
def get_context_data(self, **kw):
id = kw.get('params', kw)['id']
which is just a little bit more code but could crash in django 1.4 if
somehow there's a "params" argument
Hello,
I have the following scenario. I have multiple tenants on different
databases, all sharing the same code base. Everytime there is a change on
the models, I call south's migrate on each of the databases via a single
command migrate_all_databases (which calls south's migrate and django's
o all models needed, so that
you can infer which Tenant you are talking about. I've been thinking of
using it on my next project. Any suggestions? Thanks in advance.
Bernardo Pires
Am Mittwoch, 9. Mai 2012 05:02:45 UTC+2 schrieb Alec Taylor:
>
> Dear Django-developers,
>
> I&#x
Sorry for reviving this thread. Are the auth mixins fork from ogier going
to be commited to the django master branch anytime soon? I'd like to
"officially" use it. Is there any documentation available? Thanks in
advance.
Am Dienstag, 3. April 2012 02:35:41 UTC+2 schrieb Jacob Kaplan-Moss:
>
>
Someone has PMS.
On Jan 30, 12:22 pm, Etienne Robillard wrote:
> On 01/29/2012 02:46 PM, John Hensley wrote:
>
>
>
>
>
>
>
>
>
> > On Jan 29, 2012, at 1:52 PM, Etienne Robillard wrote:
>
> >> On 01/29/2012 01:40 PM, Aymeric Augustin wrote:
> >>> Hello Etienne,
>
> >>> The three messages you poste
That's a great reference, many thanks ivan!
On Jan 29, 4:58 pm, Ivan Kharlamov wrote:
> On 01/29/2012 12:18 PM, Bernardo Pires wrote:
>
>
>
>
>
>
>
>
>
> > Good Morning guys!
> > Scenario is the following. For some models on Django, I would like to
considering this scenario,
how would you guys rate this method, would it be ok to have one table
for each user?
The model that requires custom fields is for example Person. They
might want a custom field to store address, blood type, or any other
thing.
MANY THANKS in advance! Have a nice sunday!
much
time to it.
In any event, by now it's pretty clear that my proposal isn't all that
popular, so I'm retracting it. Thanks for all the feedback! I'll be lurking
around :)
Cheers,
rbp
--
Rodrigo Bernardo Pimentel <[EMAIL PROTECTED]> | GPG KeyId: <0x0DB1497
that Python 3.0 is not that much of a moving target either. Of
course, such a porting project would require following development of 2to3.
rbp
--
Rodrigo Bernardo Pimentel <[EMAIL PROTECTED]> | GPG KeyId: <0x0DB14978>
http://isnomore.net
--~--~-~--~~~
s, for the
reasons I explained above. The port might not be instantly suitable for a
sizeable project, but that's not the only advantage that such a port would
offer.
Thanks again for your feedback, James! I'd love to hear more from other
developers on this matter.
rbp
--
Rodrigo Bern
king on
pyk3. As for whether it should be included in trunk or as a branch, I'd like
input from my would-be mentor, as well as on what concerns external
dependencies that might also need porting.
> Anyway, good luck with the Summer of Code.
Thanks, and thanks for the feedback! :)
Cheer
be willing to mentor (or co-mentor) me on it.
Thanks!
rbp
--
Rodrigo Bernardo Pimentel <[EMAIL PROTECTED]> | GPG KeyId: <0x0DB14978>
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django
14 matches
Mail list logo
