Re: Changing MEDIA_ROOT while running tests (as in ./manage.py test)

[J . Pablo Fernández]

On Apr 22, 9:46 pm, Phil Mocek 
wrote:
> On Wed, Apr 22, 2009 at 12:22:08PM -0700, J. Pablo Fern?ndez wrote:
> > I already know about how to separate settings between development and
> > production; but that's not what I'm trying to do and I couldn't find
> > how to adapt for separating settings between development and
> > test-time. That is, I haven't found any way to make './ manage.py
> > test' pick a different settings file or be able to customize settings.
> > Do you know how?
>
> Yes.
>
> It's explained in the Django settings documentation.

Nothing in the settings documentation seems to be what I want. Again,
I don't know what you are referring to, if you are referring to
settings.configure(), by the time the test is reached it's too late.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Changing MEDIA_ROOT while running tests (as in ./manage.py test)

[J . Pablo Fernández]

On Apr 22, 10:13 pm, Phil Mocek 
wrote:
> On Wed, Apr 22, 2009 at 12:46:32PM -0700, Phil Mocek wrote:
> > [What you've repeatedly asked is] explained in the Django
> > settings documentation that I referenced earlier, that you
> > apparently did not read before asking your question or after I
> > helpfully suggested that you read it.  It's also explained by
> > the in-built usage help that manage.py provides.  You never
> > indicated where you'd already searched for the information you
> > seek, and it seems that you haven't searched at all.
>
> Sheesh, it's also explained just five paragraphs into the second
> Google search result I cited.

'./manage.py --settings_test test' and './manage.py test' is not the
same, if that's why you are referring to. There's a big difference,
the second is the command everybody runs to test the application while
the first one is much more obscure. Upon running the second one and
seeing it fail, the most likely conclusion would be "something is
broken", not "I may be missing a command line".
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Changing MEDIA_ROOT while running tests (as in ./manage.py test)

[J . Pablo Fernández]

Hello Phil,

Thanks for the answer. I already know about how to separate settings
between development and production; but that's not what I'm trying to
do and I couldn't find how to adapt for separating settings between
development and test-time. That is, I haven't found any way to make './
manage.py test' pick a different settings file or be able to customize
settings. Do you know how?

Now, regarding the reason I want to customize MEDIA_ROOT; it's to be
able to locate the files referred to by FileFields. Whether I do it
modifying it at run time or with a settings files I don't care because
it's just for a test, it's not for production. As long as it works I'm
ok.

Thanks.

On Apr 22, 4:39 pm, Phil Mocek 
wrote:
> On Tue, Apr 21, 2009 at 11:29:38PM -0700, J. Pablo Fern?ndez wrote:
> > I need to change MEDIA_ROOT while running tests, so that the files
> > pointed to in fixtures in ImageFields can be found. [...] Any ideas
> > how can I achieve this?
>
> I assume you've already searched the Web with terms like "django
> multiple settings," "django alternative settings," and "django
> development settings."  Among the top results returned by Google are:
>
> "Django settings files for development and production - Martin Jansen"
> 
>
> "Multiple django configurations for development and production ..."
> 
>
> "Ninjacipher » Blog Archive » django alternate development settings ..."
> 
>
> So that subscribers to this list can better assist you, please tell us
> what you learned from the information that is easily found on the Web,
> and what you have already tried based on that information.
>
> Also, as you're probably a considerate person who respects other
> people's time, it should be safe to assume that before you asked your
> question on this list, you searched the list archives to determine
> whether the topic has previously been discussed (because you'd be
> wasting your time and that of other subscribers if you brought it up
> again for any reason other than extending the discussion or requesting
> clarification).
>
> When I search  for
> "testing settings", the *second* result is:
>
> "media directory for testing"
> 
>
> How did the answers people already provided to Faheem Mitha's 2007
> question work out for you?
>
> > I've tried settings.MEDIA_ROOT = "blah" in the test method and in the
> > setUp method but still it tries to find the file in the wrong
> > location.
>
> Since you're having difficulty making Django settings work the way you
> want, I assume you've thoroughly read the related documentation:
>
> 
>
> In section "Altering settings at runtime" of that document:
> 
>
> is written:
>
> >> You shouldn't alter settings in your applications at runtime. For
> >> example, don't do this in a view:
>
> >>     from django.conf import settings
>
> >>     settings.DEBUG = True   # Don't do this!
>
> >> The only place you should assign to settings is in a settings file.
>
> What was your rationale for trying to do *precisely* what the Django
> authors told you not to do?
>
> See also: ,
> particularly this section:
> 
>
> --
> Phil Mocek
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Changing MEDIA_ROOT while running tests (as in ./manage.py test)

[J . Pablo Fernández]

Hello,

I need to change MEDIA_ROOT while running tests, so that the files
pointed to in fixtures in ImageFields can be found. I've tried
settings.MEDIA_ROOT = "blah" in the test method and in the setUp
method but still it tries to find the file in the wrong location. Any
ideas how can I achieve this?

Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

1.0 branch

[J . Pablo Fernández]

Hello,

Which one is the 1.0 branch on the SVN repo?

Thanks.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Download source-code feature.

[J . Pablo Fernández]

Hello,

Is there any reusable or copyable implementation of download-source-
code feature as it would be used when using the Affero GPL license?

Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Custom management command

[J . Pablo Fernández]

I would have thought Django did it by itself, or actually, manage.py.
After all, when I do manage.py shell, the pythonpath seems to be
correct for me to do import bonvortaro.

On May 15, 8:20 am, Alex Morega <[EMAIL PROTECTED]> wrote:
> On May 15, 2008, at 09:52 , J. Pablo Fernández wrote:
>
> > ImportError: 'No module named bonvortaro'
>
> > In the process of getting the commands, it tries to import the package
> > and it fails. I could try setting up the pythonpath or something like
> > that, but that would be only a workaround. There should be a better
> > solution (and doesn't everybody have this same problem?)
>
> You have to set your pythonpath to include your project. Or you can  
> symlink/move your project to a folder on the python path.
>
> In production, if you use mod_python or mod_wsgi, you can set the  
> pythonpath using their configuration options. What I do, for quick  
> development, is modify manage.py to set its own pythonpath. Add  
> something like this before the line  "from django.core.management  
> import execute_manager":
>
> import sys
> sys.path.append('/the/path/to/my/project')
>
> Cheers,
> -- Alex
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Custom management command

[J . Pablo Fernández]

It actually looks like a bug, If nobody did it, I'll try to reproduce
it this afternoon and report the bug.

On May 15, 7:52 am, J. Pablo Fernández <[EMAIL PROTECTED]> wrote:
> Ok, debuging showed me a problem.
>
> ImportError: 'No module named bonvortaro'
>
> In the process of getting the commands, it tries to import the package
> and it fails. I could try setting up the pythonpath or something like
> that, but that would be only a workaround. There should be a better
> solution (and doesn't everybody have this same problem?)
>
> Thanks.
>
> On May 14, 9:37 pm, J. Pablo Fernández <[EMAIL PROTECTED]> wrote:
>
> > Hello,
>
> > I've made a custom management command like this:
>
> > $ find -name "*.py*"
> > ./manage.py
> > ./__init__.pyc
> > ./settings.pyc
> > ./urls.py
> > ./urls.pyc
> > ./vortaro/management/commands/import_vortaro.py
> > ./vortaro/management/commands/import_vortaro.pyc
> > ./vortaro/management/commands/__init__.pyc
> > ./vortaro/management/commands/__init__.py
> > ./vortaro/management/__init__.pyc
> > ./vortaro/management/__init__.py
> > ./vortaro/models.py
> > ./vortaro/__init__.pyc
> > ./vortaro/models.pyc
> > ./vortaro/__init__.py
> > ./vortaro/views.py
> > ./__init__.py
> > ./settings.py
>
> > and:
>
> > $ cat ./vortaro/management/commands/import_vortaro.py
> > from django.core.management.base import NoArgsCommand
>
> > class Command(NoArgsCommand):
> >     help = "Import a set of xml from reta-vortaro."
> > #    args = "[datadir]"
> > #    label = "data directory"
>
> >     requires_model_validation = True
> >     can_import_settings = True
>
> >     def handle_noargs(self, **options):
> >         print("Hello world!")
> >         print("Options: %s" % options)
>
> > but it is not being picked up. ./manage.py help doesn't list it and:
>
> > $ ./manage.py import_vortaro
> > Unknown command: 'import_vortaro'
> > Type 'manage.py help' for usage.
>
> > With the manage.py shell I can import the command and run it, so
> > syntactically, everything is correct. I'm running a very recent Django
> > (r7534). Any ideas what's wrong and/or how to find out?
>
> > Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Custom management command

[J . Pablo Fernández]

Ok, debuging showed me a problem.

ImportError: 'No module named bonvortaro'

In the process of getting the commands, it tries to import the package
and it fails. I could try setting up the pythonpath or something like
that, but that would be only a workaround. There should be a better
solution (and doesn't everybody have this same problem?)

Thanks.

On May 14, 9:37 pm, J. Pablo Fernández <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I've made a custom management command like this:
>
> $ find -name "*.py*"
> ./manage.py
> ./__init__.pyc
> ./settings.pyc
> ./urls.py
> ./urls.pyc
> ./vortaro/management/commands/import_vortaro.py
> ./vortaro/management/commands/import_vortaro.pyc
> ./vortaro/management/commands/__init__.pyc
> ./vortaro/management/commands/__init__.py
> ./vortaro/management/__init__.pyc
> ./vortaro/management/__init__.py
> ./vortaro/models.py
> ./vortaro/__init__.pyc
> ./vortaro/models.pyc
> ./vortaro/__init__.py
> ./vortaro/views.py
> ./__init__.py
> ./settings.py
>
> and:
>
> $ cat ./vortaro/management/commands/import_vortaro.py
> from django.core.management.base import NoArgsCommand
>
> class Command(NoArgsCommand):
>     help = "Import a set of xml from reta-vortaro."
> #    args = "[datadir]"
> #    label = "data directory"
>
>     requires_model_validation = True
>     can_import_settings = True
>
>     def handle_noargs(self, **options):
>         print("Hello world!")
>         print("Options: %s" % options)
>
> but it is not being picked up. ./manage.py help doesn't list it and:
>
> $ ./manage.py import_vortaro
> Unknown command: 'import_vortaro'
> Type 'manage.py help' for usage.
>
> With the manage.py shell I can import the command and run it, so
> syntactically, everything is correct. I'm running a very recent Django
> (r7534). Any ideas what's wrong and/or how to find out?
>
> Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Custom management command

[J . Pablo Fernández]

On May 14, 10:48 pm, George Vilches <[EMAIL PROTECTED]> wrote:
> On May 14, 2008, at 5:23 PM, Alex Morega wrote:
>
>
>
>
>
> > On May 14, 2008, at 23:37 , J. Pablo Fernández wrote:
> >> I've made a custom management command like this:
> >> [...]
> >> but it is not being picked up. ./manage.py help doesn't list it and:
>
> >> $ ./manage.py import_vortaro
> >> Unknown command: 'import_vortaro'
> >> Type 'manage.py help' for usage.
>
> >> With the manage.py shell I can import the command and run it, so
> >> syntactically, everything is correct. I'm running a very recent  
> >> Django
> >> (r7534). Any ideas what's wrong and/or how to find out?
>
> > Hi,
>
> > I'm not sure if it matters, but have you added the 'vortaro' app to
> > INSTALLED_APPS in settings.py?
>
> It definitely matters.  Management commands *only* register for  
> installed apps, it's the only way the system knows how to find them.  
> However, if your app doesn't also have models, there could be other  
> bugs you should watch for that are currently filed in Trac.  For now,  
> just make sure you have a models.py file in there, even if you don't  
> have any contents in the file.
>
> gav

I have models and all this seems to be ok.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Custom management command

[J . Pablo Fernández]

On May 14, 10:23 pm, Alex Morega <[EMAIL PROTECTED]> wrote:
> On May 14, 2008, at 23:37 , J. Pablo Fernández wrote:
>
> > I've made a custom management command like this:
> > [...]
> > but it is not being picked up. ./manage.py help doesn't list it and:
>
> > $ ./manage.py import_vortaro
> > Unknown command: 'import_vortaro'
> > Type 'manage.py help' for usage.
>
> > With the manage.py shell I can import the command and run it, so
> > syntactically, everything is correct. I'm running a very recent Django
> > (r7534). Any ideas what's wrong and/or how to find out?
>
> Hi,
>
> I'm not sure if it matters, but have you added the 'vortaro' app to  
> INSTALLED_APPS in settings.py?

Yes, I have added it.

$ ./manage.py syncdb
...
Creating table vortaro_word
...
$

Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Custom management command

[J . Pablo Fernández]

Hello,

I've made a custom management command like this:

$ find -name "*.py*"
./manage.py
./__init__.pyc
./settings.pyc
./urls.py
./urls.pyc
./vortaro/management/commands/import_vortaro.py
./vortaro/management/commands/import_vortaro.pyc
./vortaro/management/commands/__init__.pyc
./vortaro/management/commands/__init__.py
./vortaro/management/__init__.pyc
./vortaro/management/__init__.py
./vortaro/models.py
./vortaro/__init__.pyc
./vortaro/models.pyc
./vortaro/__init__.py
./vortaro/views.py
./__init__.py
./settings.py

and:

$ cat ./vortaro/management/commands/import_vortaro.py
from django.core.management.base import NoArgsCommand

class Command(NoArgsCommand):
help = "Import a set of xml from reta-vortaro."
#args = "[datadir]"
#label = "data directory"

requires_model_validation = True
can_import_settings = True

def handle_noargs(self, **options):
print("Hello world!")
print("Options: %s" % options)

but it is not being picked up. ./manage.py help doesn't list it and:

$ ./manage.py import_vortaro
Unknown command: 'import_vortaro'
Type 'manage.py help' for usage.

With the manage.py shell I can import the command and run it, so
syntactically, everything is correct. I'm running a very recent Django
(r7534). Any ideas what's wrong and/or how to find out?

Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Widgets with an error class

[J . Pablo Fernández]

No ideas on this?

On Apr 6, 2:38 am, J. Pablo Fernández <[EMAIL PROTECTED]> wrote:
> Hello,
>
> Is there some way to add a class="error" or wrap the inputs in a  class="error"> when the field has a validationerror?
>
> Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Widgets with an error class

[J . Pablo Fernández]

Hello,

Is there some way to add a class="error" or wrap the inputs in a  when the field has a validation error?

Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Printing only the radio input

[J . Pablo Fernández]

Just for the record, I kind of fixed it and submitted the new patch,
with an added feature.

On Apr 5, 8:42 pm, J. Pablo Fernández <[EMAIL PROTECTED]> wrote:
> Thank you Nathaniel,
>
> I gave this code a try and it didn't work. It seems to be on track but
> something is broken. I've submitted a comment about it to the issue
> itself.
>
> Thank you.
>
> On Apr 5, 4:36 pm, Nathaniel Whiteinge <[EMAIL PROTECTED]> wrote:
>
> > On Apr 5, 6:36 am, J. Pablo Fernández <[EMAIL PROTECTED]> wrote:
>
> > > and what I want to do is print the individuals  > > type="radio" ...> without any label, list or anything.
>
> > No, this isn't currently possible.
>
> > If you don't mind patching your Django installation, there's a ticket
> > [1] with a patch that talks about exactly this. There's been talk
> > recently on the django-dev list about changes to how forms are
> > rendered which will, hopefully, allow this flexibility, but that's a
> > long way off.
>
> > .. [1]http://code.djangoproject.com/ticket/6458
> > .. 
> > [2]http://groups.google.com/group/django-developers/browse_thread/thread...
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Printing only the radio input

[J . Pablo Fernández]

Thank you Nathaniel,

I gave this code a try and it didn't work. It seems to be on track but
something is broken. I've submitted a comment about it to the issue
itself.

Thank you.

On Apr 5, 4:36 pm, Nathaniel Whiteinge <[EMAIL PROTECTED]> wrote:
> On Apr 5, 6:36 am, J. Pablo Fernández <[EMAIL PROTECTED]> wrote:
>
> > and what I want to do is print the individuals  > type="radio" ...> without any label, list or anything.
>
> No, this isn't currently possible.
>
> If you don't mind patching your Django installation, there's a ticket
> [1] with a patch that talks about exactly this. There's been talk
> recently on the django-dev list about changes to how forms are
> rendered which will, hopefully, allow this flexibility, but that's a
> long way off.
>
> .. [1]http://code.djangoproject.com/ticket/6458
> .. [2]http://groups.google.com/group/django-developers/browse_thread/thread...
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Printing only the radio input

[J . Pablo Fernández]

Hello,

I have a ChoicesField defined like this:

blah = forms.ChoiceField(
choices=SOME_CHOICES,
widget=forms.RadioSelect,
initial=SOME_CHOICES[0][0])

and what I want to do is print the individuals  without any label, list or anything. The reason to
do that is because I have a very weird-shaped form.

Is that possible? If so, how?

Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Models that are ordered lists

[J . Pablo Fernández]

Hello,

Is there some tool in Django to make a model an ordered list where a
position field is stored in the database and methods like move_up() or
move_down() do the right thing?

If not, how would I go about doing it so it is reusable? a class to inherit
from in model classes (as the second class to inherit from)?

Thanks.
-- 
J. Pablo Fernández <[EMAIL PROTECTED]> (http://pupeno.com)


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Email as primary key in users

[J . Pablo Fernández]

Hello Sebastjan,

That means I would not be using djanago.contrib.auth.views.login, right?


Sebastjan Trepca wrote:
> Sure,
> 
> you just use email field when authenticating user.
> 
> Like this:
> 
> from django.contrib.auth import authenticate
> user = authenticate(email='[EMAIL PROTECTED]', password='secret')
> if user is not None:
> if user.is_active:
> print "You provided a correct username and password!"
> else:
> print "Your account has been disabled!"
> else:
> print "Your username and password were incorrect."
> 
> Sebastjan
> 
> On 1/20/08, J. Pablo Fern�ndez <[EMAIL PROTECTED]> wrote:
>>
>> Hello,
>> Is it possible to use email instead of username for users. So for logging
>> in I would ask email and password (no username)?
>> Thanks.
>> --
>> J. Pablo Fern�ndez <[EMAIL PROTECTED]> (http://pupeno.com)
>>
>>
>> >
>>
> 
> 
-- 
J. Pablo Fernández <[EMAIL PROTECTED]> (http://pupeno.com)


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Email as primary key in users

[J . Pablo Fernández]

Hello,
Is it possible to use email instead of username for users. So for logging in
I would ask email and password (no username)?
Thanks.
-- 
J. Pablo Fernández <[EMAIL PROTECTED]> (http://pupeno.com)


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---