Re: starting a django project

2014-03-19 Thread Venkatraman S
Are you using any tutorials to get started?
Also, is this on Windows or Linux - shouldnt be much different; you might
have some PATH issues in certain cases.
Also, you haven't mentioned if you got any errors/warnings while starting
the project.

-Venkat
@venkasub 



On Tue, Mar 18, 2014 at 11:02 PM, aparajith sundar wrote:

> HI, i am a first time django user. i have successfully installed django
> but when i try running this "django-admin.py startproject mysite" code
> all i get is the django-admin text file! i have tried adding different
> paths and changing all types of settings but its to no avail.. i am told i
> should be creating a new directory by the name of mysite but nothing of
> that sort is happening. could someone please help me out with this?!?!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/3f6a0aec-d4bd-4764-82b7-0fcc57f4b0dd%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAN7tdFQspj6VVPXjOC-FpOVf_sJPMQDbih0qD1oScfrxtZEn_w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Moving the focus from the 'Save' button to the 'Save and add another' one

2014-03-19 Thread Venkatraman S
To get you started rather then spoonfeeding you : Have you looked at the
code which generates this button? Can you think of possible javascript
alterations that you can do to change the focus or order?

-V


On Sun, Mar 16, 2014 at 1:10 AM, vittorio  wrote:

> My 1.6.2 django app deals  with a warehouse management using the admin
> interface exclusively.
>  I've been asked to make it possible to use  barcode readers  for
> recording flows of items going either in or out of the warehouse (see the
> attached admin form using inlines),  Because our bar code readers use the
> standard RETURN (ascii 13) code to close the read string (and it's better
> not to modify this standard for other uses)  I would like to make the 'Save
> and add another' (In Italian 'Salva e aggiungi un altro') the default
> button triggered by the RETURN (ascii 13).
> Could you please help me to do this taking into account that I'm a real
> newbie who needs kind of a tutorial step by step.
> Thank you
> Vittorio
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/6da94d42-a40a-4791-a8fd-aec58e72b90c%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAN7tdFRMQQZjG-pGM9%2B%2BckCHJ6wgGuYKFtD-A_rUxRNK-_pRgQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Django Logging database queries

2014-03-19 Thread Venkatraman S
INSERT/UPDATE/DELETE/SELECT cover almost all types that will be used. What
else is getting logged?

And what do you mean by 'FAILED' Select queries? Do you mean Timed-out ones?



On Thu, Mar 13, 2014 at 12:32 PM, Anju SB  wrote:

> Dear All,
>
> I am a newbie in Django programming and developing a web application
> using django 1.3 and postgresql.  I want to log insert, update, delete and
> failed select queries in my daily log file.  I configured  
> 'django.db.backends'
> in the logger of the Logging dict in Settings.py.   But I get all the
> queries in that application. I need only insert, update, delete and failed
> select queries.
>
> Please help me to move on
>
> Thanking you
> Anju
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/f5d6457e-9b23-4395-86c0-89f673689d46%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAN7tdFQ-A%2BhU6%3DRmzDy5Mje4ErpeXmrJ1z9m4Fn4nMjeZTo0Zg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Using Redis as a DB backend for some models (not a caching backend!)

2014-03-19 Thread Venkatraman S
Good Q. Something along the lines of :
https://docs.djangoproject.com/en/dev/topics/db/multi-db/  ?
Let us know what you find.

On Sat, Mar 15, 2014 at 1:10 AM, Alon Nisser  wrote:

> Can I use redis as a django database for some of my models? I'm aware (and
> using) caching with django and redis, but I'm looking for something else
> here: Something I can use at least some of the orm features with, handle a
> django Model, etc.  I found 
> django-redis-enginebut 
> it doesn't look like an active project (pre alpha commits 3 years ago)
> and django-nonrel  which doesn't
> support redis and is actually a django fork and not Django proper. Any
> ideas how to proceed from here? Thanks!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/33b35731-711b-4730-bda5-0a1d9c0ffc81%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAN7tdFSY81q1g0TnUXzJ13707gtiwjaA_GBSSeOY6Tg3pDUPqQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Review needed

2014-03-19 Thread Venkatraman S
Why do you want to do this! It looks complicated and badly formed.

-V


On Mon, Mar 3, 2014 at 12:11 AM, Kakar Nyori  wrote:

> Hello,
> This may be long, but I really need your help. I have a class *Asset*,
> which is the *base class* of another *classes *(like *Photo, Question,
> Video etc.*) Basically its a *Multiple Table Inheritance*. I need this to
> get all the post or all the *objects* of the user. And it does what I
> want. But I saw that, many were against *Multiple Table Inheritance, *or
> if not they discouraged MTI. So, I really need to know that, *how much
> will it matter*? Or is there any other way to achieve it. To get all the
> objects of a *User*? Please help me decide what to do. If I am not clear,
> please ask me. I will really appreciate if anyone would guide me through
> this.
>
> Thank you.
>
> *This are my models:*
>
>
> class Asset(models.Model):
> user = models.ForeignKey(User, related_name = "user_objects")
> likes = models.ManyToManyField(User, through="Like",
> related_name="Liked_user")
> comments = models.ManyToManyField(User, through="Comment",
> related_name="Commented_user")
> timestamp = models.DateTimeField(auto_now = True, auto_now_add= False)
> updated = models.DateTimeField(auto_now = False, auto_now_add = True)
>
> class Meta:
> ordering = ['-timestamp']
>
> def __unicode__(self):
> return self.__class__.__name__
>
> class Like(models.Model):
> asset = models.ForeignKey(Asset)
> liked_by = models.ForeignKey(User)
> liked_time = models.DateTimeField(auto_now = True, auto_now_add = False)
>
> def __unicode__(self):
> return "%s likes %s" % (self.liked_by, self.asset)
>
> class Comment(models.Model):
> asset = models.ForeignKey(Asset)
> comment_by = models.ForeignKey(User)
> liked_time = models.DateTimeField(auto_now = True, auto_now_add = False)
>
> def __unicode__(self):
> return "%s likes %s" % (self.comment_by, self.asset)
>
> def get_upload_file_name(instance, filename):
> return "uploaded_files/%s_%s" %(str(time()).replace('.','_'), filename)
>
> class Album(Asset):
> title = models.CharField(max_length=200)
> description = models.TextField()
>
> def __unicode__(self):
> return self.__class__.__name__
>
>
> class Picture(Asset):
> description = models.TextField()
> image = models.ImageField(upload_to=get_upload_file_name)
> album = models.ForeignKey(Album, null=True, blank=True, default = None)
>
> def __unicode__(self):
> return self.__class__.__name__
>
> class BackgroundImage(Picture):
> pass
>
> class ProfilePicture(Picture):
> pass
>
> class Tag(models.Model):
> title = models.CharField(max_length=40)
> description = models.TextField()
>
> def __unicode__(self):
> return self.title
>
> class Question(Asset):
> title = models.CharField(max_length=200)
> description = models.TextField()
> tags = models.ManyToManyField(Tag)
>
> def __unicode__(self):
> return self.title
>
> class Answer(Asset):
> description = models.TextField()
> question = models.ForeignKey(Question)
>
> def __unicode__(self):
> return self.description
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/871d20b8-17a3-4ed4-bb8e-3c0befb5121f%40googlegroups.com
> .
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAN7tdFT8krBHrLjvSy7Hn35mAk0%2BBDXvOgcpXjNX_wMOZg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: "Beginning Geo Django: Rich Gis Web Applications With Python" Where can I get the book?

2014-03-19 Thread Max Demars
Hi Alex,

I cannot help you with this book in particular, but I could suggest another 
book that helped me a lot.

Python Geospatial Development by Erik Westra

-Max Demars

On Tuesday, March 18, 2014 11:49:49 AM UTC-4, Alex wrote:
>
> Thats an interesting dilemma. I just looked around a no one has copies. 
> The publisher says "The eBook version of this title will be available 
> soon" 
> http://www.springer.com/computer/book/978-1-4302-2532-4 
>
> But I have no idea how long it's said that. 
>
> This appears to be the ISBN for the printed version 9781430225317 
> Some searches show it on back order at every store. 
>
> So yes it seems limited quantities and no eBook version yet. Maybe 
> contact Apress and ask when the eBook will be available. 
>
> Thanks, 
> Alex 
>
> FYI: I'm forwarding this to the Geodjango mailing list, you might want 
> to join it and ask more there. geod...@googlegroups.com  
>
> On 03/16/2014 07:43 PM, ruomu sh wrote: 
> > Yes I understand. But I could not figure out how can I get it here at 
> > Nepal. I will buy it. I find different price listed on internet. Some 
> site 
> > say it is out of stock. Is it published only limited copies? 
> > 
> > On Friday, February 21, 2014 6:47:20 PM UTC+5:45, Tom Evans wrote: 
> >> 
> >> On Fri, Feb 21, 2014 at 10:15 AM, Ram Shrestha 
> >> > 
>
> >> wrote: 
> >>> Dear All, 
> >>> I am want to learn GeoDjango in real world application. I believe this 
> >> book 
> >>> "Beginning Geo Django: Rich Gis Web Applications With Python" is the 
> >> best 
> >>> book for me. But I could not download download it. 
> >>> 
> >>> If anyone have this book Please share the book with me. Where can I 
> get 
> >> it 
> >>> for free! 
> >> 
> >> If the author or publisher does not make this book available as a free 
> >> download, it is not appropriate to use this list to try to pirate it. 
> >> 
> >> Doing so discourages future authors and publishers from writing books 
> >> about Django. 
> >> 
> >> 
> >> Cheers 
> >> 
> >> Tom 
> >> 
> > 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/aa515ed2-9e2b-4b91-924e-dc34e374d8c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [GeoDjango] Re: "Beginning Geo Django: Rich Gis Web Applications With Python" Where can I get the book?

2014-03-19 Thread Michael Savarese
That's a good book for all things GIS/Python as well as a GeoDjango example.

These links may help out also. They use Leaflet
instead of the GeoDjango built-in OpenLayers

https://github.com/makinacorpus/django-leaflet

http://blog.mathieu-leplatre.info/geodjango-maps-with-leaflet.html


On Wed, Mar 19, 2014 at 8:34 AM, Max Demars  wrote:

> Hi Alex,
>
> I cannot help you with this book in particular, but I could suggest
> another book that helped me a lot.
>
> Python Geospatial Development by Erik Westra
>
> -Max Demars
>
>
> On Tuesday, March 18, 2014 11:49:49 AM UTC-4, Alex wrote:
>
>> Thats an interesting dilemma. I just looked around a no one has copies.
>> The publisher says "The eBook version of this title will be available
>> soon"
>> http://www.springer.com/computer/book/978-1-4302-2532-4
>>
>> But I have no idea how long it's said that.
>>
>> This appears to be the ISBN for the printed version 9781430225317
>> Some searches show it on back order at every store.
>>
>> So yes it seems limited quantities and no eBook version yet. Maybe
>> contact Apress and ask when the eBook will be available.
>>
>> Thanks,
>> Alex
>>
>> FYI: I'm forwarding this to the Geodjango mailing list, you might want
>> to join it and ask more there. geod...@googlegroups.com
>>
>> On 03/16/2014 07:43 PM, ruomu sh wrote:
>> > Yes I understand. But I could not figure out how can I get it here at
>> > Nepal. I will buy it. I find different price listed on internet. Some
>> site
>> > say it is out of stock. Is it published only limited copies?
>> >
>> > On Friday, February 21, 2014 6:47:20 PM UTC+5:45, Tom Evans wrote:
>> >>
>> >> On Fri, Feb 21, 2014 at 10:15 AM, Ram Shrestha 
>> >> wrote:
>> >>> Dear All,
>> >>> I am want to learn GeoDjango in real world application. I believe
>> this
>> >> book
>> >>> "Beginning Geo Django: Rich Gis Web Applications With Python" is the
>> >> best
>> >>> book for me. But I could not download download it.
>> >>>
>> >>> If anyone have this book Please share the book with me. Where can I
>> get
>> >> it
>> >>> for free!
>> >>
>> >> If the author or publisher does not make this book available as a free
>> >> download, it is not appropriate to use this list to try to pirate it.
>> >>
>> >> Doing so discourages future authors and publishers from writing books
>> >> about Django.
>> >>
>> >>
>> >> Cheers
>> >>
>> >> Tom
>> >>
>> >
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "geodjango" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to geodjango+unsubscr...@googlegroups.com.
> To post to this group, send email to geodja...@googlegroups.com.
> Visit this group at http://groups.google.com/group/geodjango.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CANhS580%3Dy5D016MPHsHnm%2B9fidRQJZao06%2BmOp2NfxoF3h17rw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: I am unable to get the choice field to validate on creating users. it doesn't make sense at all.

2014-03-19 Thread Tom Evans
On Wed, Mar 19, 2014 at 3:40 PM, sashank reddy
 wrote:
> Hi,
>
> I have been trying to extend the UserCreationForm and have a form which
> performs user registration and adds email and the names.
> In addition I am using a choice field that allows a list down of existing
> groups so that you can assign the user to an group immediately  upon
> creation.
>
> The problem is that, if I create a new group, and try to add users to it,
> then the form validation fails.
> I have restart the django server or wait for it to reset internally and show
> "Validating models ..". Then it starts to work.
>
> The following is the code snippet:
> =
> def choice_desig():
> choice_desig = []
> g = Group.objects.all()
> for k in g:
> choice_desig.append((k.name, k.name))
> return choice_desig
>
> class New_user_form(UserCreationForm):
> email = forms.EmailField(required=True)
> first_name = forms.CharField(required=True)
> last_name = forms.CharField(required=True)
> desig_group = forms.ChoiceField(choices=choice_desig())

If you use choice_desig() function like that, it will get called once,
when the server initially parses that file. It will never be run again
until the server re-parses that file.

You could pass a callable to choices - "choices=choice_desig".

However, the right solution for when you want a form field to choose a
model instance is to use a form.ModelChoiceField.

Cheers

Tom

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAFHbX1JrMayWP8SHN1Vz5MT28yseK%2Br_YqEUx%3DktNMMGOyRMBg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Django Form Wizard - Something wrong?

2014-03-19 Thread BadStorm
Hi,
I try to add a wizard in my project. I read the documentation at 
https://docs.djangoproject.com/en/dev/ref/contrib/formtools/form-wizard/ 
and I followed step by step those instructions.
The only thing i change is that I added a third step.
The problem is: when I try  to fill all the fields for all the steps and at 
the end I go back Django lose data that I entered before. Only on the first 
step, datas remain, but no on the others.
I used the same code of the documentation. What can be the matter?

Thanks a lot.

Regards

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/51da1576-6280-49c2-bde3-8893df2371c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


I am unable to get the choice field to validate on creating users. it doesn't make sense at all.

2014-03-19 Thread sashank reddy
Hi,

I have been trying to extend the UserCreationForm and have a form which 
performs user registration and adds email and the names.
In addition I am using a choice field that allows a list down of existing 
groups so that you can assign the user to an group immediately  upon 
creation.

The problem is that, if I create a new group, and try to add users to it, 
then the form validation fails.
I have restart the django server or wait for it to reset internally and 
show "Validating models ..". Then it starts to work.

The following is the code snippet:
=
def choice_desig():
choice_desig = []
g = Group.objects.all()
for k in g:
choice_desig.append((k.name, k.name))
return choice_desig

class New_user_form(UserCreationForm):
email = forms.EmailField(required=True)
first_name = forms.CharField(required=True)
last_name = forms.CharField(required=True)
desig_group = forms.ChoiceField(choices=choice_desig())

def save(self, commit=True):
user = super(UserCreationForm, self).save(commit=False)
user.set_password(self.cleaned_data["password1"])
user.email = self.cleaned_data["email"]
user.first_name = self.cleaned_data["first_name"]
user.last_name = self.cleaned_data["last_name"]
designation = self.cleaned_data["desig_group"]
if commit:
user.save()
p = person.objects.get(pk=employee_id)
u = user_maps(user_name=user.username, emp_id=p)
u.save()
g = Group.objects.filter(name=designation)
print("acquired group", g[0].name)
#user.groups.add(g)
g[0].user_set.add(user)
g[0].save()
return user

def register_user(request):
if request.method == 'POST':
print("Register user : POST")
print("request.POST = ", request.POST)
form = New_user_form(request.POST)
if form.is_valid():
print("Form Validated")
new_user = form.save()
context = {}
print_user(new_user)
host = request.get_host()
link = "http://"+host +"/hr_base/index"
#return HttpResponseRedirect("http://"+host +"/hr_base/index")
return HttpResponseRedirect("/hr_base/index")
else:
print("Forms non field error", form.non_field_errors())
print("Form invalid")
print("choice_desig = ",choice_desig())
emp_id = request.POST.get('emp_id')
#host = request.get_host()
#link = "http://"+host +"/hr_base/index"
#return HttpResponseRedirect("http://"+host +"/hr_base/index")
return HttpResponseRedirect("/emp_users/new_user")
else:
print("Non post method")
print("Acquired emp_id: ", request.session['emp_id'])
form = New_user_form()
#form.acquire_groups()
#print("Form desig choice : ", form.choice_desig)
g = Group.objects.all()
desig = []
for k in g:
desig.append(k.name)
args = {}
args.update(csrf(request))
args.update({'user':request.user.username,
'form':form,
'STATIC_URL':settings.STATIC_URL,
'is_user_authenticated': request.user.is_authenticated(),
'is_user_superuser':request.user.is_superuser,
'desig': desig,})
res= render_to_response('emp_users/register.html', args)
return res

print("general area")
return HttpResponse("Doesn't Make sense")
===
Below is the template:
==
Register

{% csrf_token %}


Username:


Required. 30 characters or fewer. Letters, 
digits and @/./+/-/_ only.



Password:





Password confirmation:


Enter the same password as above, for 
verification.



email


Enter your email id, for verification.



First name:





Last name:





Group/Designation:


{% for i in desig %}
{{ i }}
{% endfor %}








I did some debugging on my own and I was surprised.
The validation error is for the select field desig_group and it fails 
somewhere just after self.validate(value) in the field.clean method.
The prints clearly indicate that the method passed and completed.

def validate(self, value):
print("Validating. value = ", value, "Empty validator result = ", 
value in validators.EMPTY_VALUES, "self.required = ", self.required)
if value in validators.EMPTY_VALUES and self.required:
print("validating: empty values =", validators.EMPTY_VALUES)
print("validating: self.required =", self.required)
raise ValidationError(self.error_messages['required'])
print("Validation complete")
def clean(self, value):
"""
Validates the given value and returns its "cleaned" value as an
appropriate Python object.

Raises ValidationError for any errors.
"""
print("Field cleaning")
value = self.to_python(value)
print("Field got value by to_python :", value)
self.validate(value)
print("Field executing validators : ")
self.run_validators(value)
print("Completed executing field validator")
return value

For these prints, I got this in my console:
=
BaseForm: 

Re: I am unable to get the choice field to validate on creating users. it doesn't make sense at all.

2014-03-19 Thread sashank reddy

Hi Tom,

What do you mean callable?
I tried changing
desig_group = forms.ChoiceField(choices=choice_desig()) 
to
desig_group = forms.ChoiceField(choices=choice_desig)

It gave error 'function' object is not iterable. 
But I want to know if the following would work.

desig = forms.ModelChoiceField(queryset=Group.objects.all())

But how do I change my view and template for it.
Can you please correct my view and template.

Regards,
Preetam

On Wednesday, 19 March 2014 21:43:39 UTC+5:30, Tom Evans wrote:
>
> On Wed, Mar 19, 2014 at 3:40 PM, sashank reddy 
> > wrote: 
> > Hi, 
> > 
> > I have been trying to extend the UserCreationForm and have a form which 
> > performs user registration and adds email and the names. 
> > In addition I am using a choice field that allows a list down of 
> existing 
> > groups so that you can assign the user to an group immediately  upon 
> > creation. 
> > 
> > The problem is that, if I create a new group, and try to add users to 
> it, 
> > then the form validation fails. 
> > I have restart the django server or wait for it to reset internally and 
> show 
> > "Validating models ..". Then it starts to work. 
> > 
> > The following is the code snippet: 
> > 
> = 
>
> > def choice_desig(): 
> > choice_desig = [] 
> > g = Group.objects.all() 
> > for k in g: 
> > choice_desig.append((k.name, k.name)) 
> > return choice_desig 
> > 
> > class New_user_form(UserCreationForm): 
> > email = forms.EmailField(required=True) 
> > first_name = forms.CharField(required=True) 
> > last_name = forms.CharField(required=True) 
> > desig_group = forms.ChoiceField(choices=choice_desig()) 
>
> If you use choice_desig() function like that, it will get called once, 
> when the server initially parses that file. It will never be run again 
> until the server re-parses that file. 
>
> You could pass a callable to choices - "choices=choice_desig". 
>
> However, the right solution for when you want a form field to choose a 
> model instance is to use a form.ModelChoiceField. 
>
> Cheers 
>
> Tom 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/37f3f382-7cdd-4331-8fd5-174ec5713cd1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: ImportError: No module named core in django 1.5.5

2014-03-19 Thread Alex Scoble
Never mind on this one. Ended up creating a virtual environment and running 
django in that and it's working now.

Thanks,

Alex

On Tuesday, March 18, 2014 10:32:01 AM UTC-7, Alex Scoble wrote:
>
> Hi All,
>
> Running CentOS 6.4 with python 2.6.6 and django 1.5.5
>
> Doing this at prompt works: python -c 'import django; print 
> django.VERSION'
> Returns: (1, 5, 5, 'final', 0)
>
> However, running django-admin.py or 
>
> import django
>
> from django.core.management import execute_from_command_line
>
> when in Python result in errors such as
>
> Traceback (most recent call last):
>   File "/usr/lib/python2.6/site-packages/django/bin/django-admin.py", line 
> 2, in 
> from django.core import management
> ImportError: No module named core
>
>
> or 
>
> Traceback (most recent call last):
>   File "", line 1, in 
> ImportError: No module named core.management
>
>
> Django 1.5.4 was running fine on this box. I'm not using virtual 
> environments and it doesn't look like those are required for what I'm doing 
> (running webvirtmgr https://github.com/retspen/webvirtmgr ). I've 
> uninstalled and reinstalled django using pip and still have same issues.
>
> Any ideas on what to check?
>
> Thanks,
>
> Alex
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/e4b5bb7d-c9ed-4f3b-9ce7-b343277b00d2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Middleware being called twice for every request, help?

2014-03-19 Thread Tyler Bettilyon
Hello!

I recently switched my Django environment from using Apache to Gunicorn. 
After this switch we noticed that our middleware was being called twice for 
each request. To confirm my suspicion I wrote a new piece of middleware: 

class TemporaryMiddleware(object):
def process_request(self, request):
if not hasattr(request, '_secret'):
request._secret = uuid.uuid4()
logging.info("set secret to {0}".format(request._secret))
else:
logging.info(request._secret)


def process_response(self, request, response):
logging.info("response {0}{1}".format(request._secret, 
response.status_code))
return response

After registering my TemporaryMiddleware I headed back to the logs:
INFO 2014-03-19 09:32:23,397 middleware.py:26] set secret to 
bb89e0ab-a30b-42ce-800b-7129a3b323ae
INFO 2014-03-19 09:32:23,398 middleware.py:28] 
bb89e0ab-a30b-42ce-800b-7129a3b323ae
INFO 2014-03-19 09:32:23,841 middleware.py:32] response 
bb89e0ab-a30b-42ce-800b-7129a3b323ae200
INFO 2014-03-19 09:32:24,126 middleware.py:32] response 
bb89e0ab-a30b-42ce-800b-7129a3b323ae200

If the only change I make is to start the server using:
python manage.py runserver

Instead of:
python manage.py run_gunicorn

my logs say:
INFO 2014-03-19 09:48:25,325 middleware.py:26] set secret to 
84b011f9-1689-4b2f-8202-01840c249937
INFO 2014-03-19 09:48:25,842 middleware.py:33] response 
84b011f9-1689-4b2f-8202-01840c249937200

It seems to me that every request is being processed twice. This happens 
regardless of the number of threads or workers available, and when I run 
with more than 1 worker and/or more than one thread the process and thread 
id's for all four logging statements are the same. So I believe one thread 
is running through all of my middleware twice per request.  

Has anyone seem anything like this before, or have any idea what might be 
going on? I've only been Djangoing for ~6 months and sometimes 
configuration stuff still escapes me. 

Thanks,
Tyler Bettilyon

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/684d2911-715e-4e6a-9ad9-ceda71607c22%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Middleware being called twice for every request, help?

2014-03-19 Thread Nikolas Stevenson-Molnar
Are you making the request from a browser? If so, your browser is
probably making an extra request for the favicon. So if your middleware
handles /all/ requests (even ones that ultimately result in 404) then
it'll be executed twice. It will look like it's twice for one request,
but it's actually two separate requests.

_Nik

On 3/19/2014 10:00 AM, Tyler Bettilyon wrote:
> Hello!
>
> I recently switched my Django environment from using Apache to
> Gunicorn. After this switch we noticed that our middleware was being
> called twice for each request. To confirm my suspicion I wrote a new
> piece of middleware:
>
> class TemporaryMiddleware(object):
> def process_request(self, request):
> if not hasattr(request, '_secret'):
> request._secret = uuid.uuid4()
> logging.info("set secret to {0}".format(request._secret))
> else:
> logging.info(request._secret)
>
>
> def process_response(self, request, response):
> logging.info("response {0}{1}".format(request._secret,
> response.status_code))
> return response
>
> After registering my TemporaryMiddleware I headed back to the logs:
> INFO 2014-03-19 09:32:23,397 middleware.py:26] set secret to
> bb89e0ab-a30b-42ce-800b-7129a3b323ae
> INFO 2014-03-19 09:32:23,398 middleware.py:28]
> bb89e0ab-a30b-42ce-800b-7129a3b323ae
> INFO 2014-03-19 09:32:23,841 middleware.py:32] response
> bb89e0ab-a30b-42ce-800b-7129a3b323ae200
> INFO 2014-03-19 09:32:24,126 middleware.py:32] response
> bb89e0ab-a30b-42ce-800b-7129a3b323ae200
>
> If the only change I make is to start the server using:
> python manage.py runserver
>
> Instead of:
> python manage.py run_gunicorn
>
> my logs say:
> INFO 2014-03-19 09:48:25,325 middleware.py:26] set secret to
> 84b011f9-1689-4b2f-8202-01840c249937
> INFO 2014-03-19 09:48:25,842 middleware.py:33] response
> 84b011f9-1689-4b2f-8202-01840c249937200
>
> It seems to me that every request is being processed twice. This
> happens regardless of the number of threads or workers available, and
> when I run with more than 1 worker and/or more than one thread the
> process and thread id's for all four logging statements are the same.
> So I believe one thread is running through all of my middleware twice
> per request. 
>
> Has anyone seem anything like this before, or have any idea what might
> be going on? I've only been Djangoing for ~6 months and sometimes
> configuration stuff still escapes me.
>
> Thanks,
> Tyler Bettilyon
> -- 
> You received this message because you are subscribed to the Google
> Groups "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to django-users+unsubscr...@googlegroups.com
> .
> To post to this group, send email to django-users@googlegroups.com
> .
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/684d2911-715e-4e6a-9ad9-ceda71607c22%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/5329D8D8.3000400%40consbio.org.
For more options, visit https://groups.google.com/d/optout.


Re: Middleware being called twice for every request, help?

2014-03-19 Thread Tom Evans
On Wed, Mar 19, 2014 at 5:50 PM, Nikolas Stevenson-Molnar
 wrote:
> Are you making the request from a browser? If so, your browser is probably
> making an extra request for the favicon.

Two requests that just happened to generate the same random uuid, and
skipped all other middleware processing apart from process_response?
Unlikely!

OP, you might want to repost, explicitly pointing out (in the subject)
that this only happens when you use run_gunicorn and never happens
when you use runserver.

Cheers

Tom

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAFHbX1J5rA7RwENk7CwOw8KZcEOEhb7VQNWxeBvXX%3DH654tjwQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Middleware being called twice for every request, help?

2014-03-19 Thread Xavier Ordoquy
Hi,

Just remove the Django debug toolbar.
It will call your middlewares to display the result.

Regards,
Xavier,
Linovia.

Le 19 mars 2014 à 18:00, Tyler Bettilyon  a écrit :

> Hello!
> 
> I recently switched my Django environment from using Apache to Gunicorn. 
> After this switch we noticed that our middleware was being called twice for 
> each request. To confirm my suspicion I wrote a new piece of middleware: 
> 
> class TemporaryMiddleware(object):
> def process_request(self, request):
> if not hasattr(request, '_secret'):
> request._secret = uuid.uuid4()
> logging.info("set secret to {0}".format(request._secret))
> else:
> logging.info(request._secret)
> 
> 
> def process_response(self, request, response):
> logging.info("response {0}{1}".format(request._secret, 
> response.status_code))
> return response
> 
> After registering my TemporaryMiddleware I headed back to the logs:
> INFO 2014-03-19 09:32:23,397 middleware.py:26] set secret to 
> bb89e0ab-a30b-42ce-800b-7129a3b323ae
> INFO 2014-03-19 09:32:23,398 middleware.py:28] 
> bb89e0ab-a30b-42ce-800b-7129a3b323ae
> INFO 2014-03-19 09:32:23,841 middleware.py:32] response 
> bb89e0ab-a30b-42ce-800b-7129a3b323ae200
> INFO 2014-03-19 09:32:24,126 middleware.py:32] response 
> bb89e0ab-a30b-42ce-800b-7129a3b323ae200
> 
> If the only change I make is to start the server using:
> python manage.py runserver
> 
> Instead of:
> python manage.py run_gunicorn
> 
> my logs say:
> INFO 2014-03-19 09:48:25,325 middleware.py:26] set secret to 
> 84b011f9-1689-4b2f-8202-01840c249937
> INFO 2014-03-19 09:48:25,842 middleware.py:33] response 
> 84b011f9-1689-4b2f-8202-01840c249937200
> 
> It seems to me that every request is being processed twice. This happens 
> regardless of the number of threads or workers available, and when I run with 
> more than 1 worker and/or more than one thread the process and thread id's 
> for all four logging statements are the same. So I believe one thread is 
> running through all of my middleware twice per request.  
> 
> Has anyone seem anything like this before, or have any idea what might be 
> going on? I've only been Djangoing for ~6 months and sometimes configuration 
> stuff still escapes me. 
> 
> Thanks,
> Tyler Bettilyon
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-users/684d2911-715e-4e6a-9ad9-ceda71607c22%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/C3E41B15-9ADC-4C69-8D0B-4DDB83C1EDBE%40linovia.com.
For more options, visit https://groups.google.com/d/optout.


Re: Middleware being called twice for every request, help?

2014-03-19 Thread Nikolas Stevenson-Molnar
Ah yes. I missed/ignored the UUIDs entirely!

_Nik

On 3/19/2014 11:08 AM, Tom Evans wrote:
> On Wed, Mar 19, 2014 at 5:50 PM, Nikolas Stevenson-Molnar
>  wrote:
>> Are you making the request from a browser? If so, your browser is probably
>> making an extra request for the favicon.
> Two requests that just happened to generate the same random uuid, and
> skipped all other middleware processing apart from process_response?
> Unlikely!
>
> OP, you might want to repost, explicitly pointing out (in the subject)
> that this only happens when you use run_gunicorn and never happens
> when you use runserver.
>
> Cheers
>
> Tom
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/5329E6AD.70100%40consbio.org.
For more options, visit https://groups.google.com/d/optout.


Simple User login not working.

2014-03-19 Thread Don Fox
My project has two superusers who have access to the Django Administration 
and who manually add about 15 Users who should then be able to login and 
use the site to do data entry.

I'm using the standard code in my views


*def auth_view(request):*
*username = request.POST.get('username',' ')*
*password = request.POST.get('password',' ')*
*user = auth.authenticate(username=username, password=password)*

*if user is not None:*
*auth.login(request, user)*
*return HttpResponseRedirect('/accounts/loggedin')*
*else:*
*return HttpResponseRediredt('/accounts/invalid') *


This should check against the users listed in the admin page?


[image: ]


However ther is no acknowledgement from the loggedin.hml template.


Does anything come to mind that I have newgelected to do to get the login 
to work.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/23a01c55-436b-4514-8be4-ed6a6915f879%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


error: 'module' object has no attribute '_handlerList'

2014-03-19 Thread Sergey R

i started to get 500 error when loading the site

traceback shows:

Traceback (most recent call last):
  File "./manage.py", line 10, in 
execute_from_command_line(sys.argv)
  File 
"/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 399, in execute_from_command_line
utility.execute()
  File 
"/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 392, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
  File 
"/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 261, in fetch_command
commands = get_commands()
  File 
"/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 107, in get_commands
apps = settings.INSTALLED_APPS
  File "/usr/local/lib/python2.7/dist-packages/django/conf/__init__.py", 
line 54, in __getattr__
self._setup(name)
  File "/usr/local/lib/python2.7/dist-packages/django/conf/__init__.py", 
line 50, in _setup
self._configure_logging()
  File "/usr/local/lib/python2.7/dist-packages/django/conf/__init__.py", 
line 76, in _configure_logging
logging_config_func(DEFAULT_LOGGING)
  File "/usr/local/lib/python2.7/dist-packages/django/utils/dictconfig.py", 
line 555, in dictConfig
dictConfigClass(config).configure()
  File "/usr/local/lib/python2.7/dist-packages/django/utils/dictconfig.py", 
line 323, in configure
del logging._handlerList[:]
AttributeError: 'module' object has no attribute '_handlerList'


last thing i remember doing was installing celery
to make this error disappear i have to  add LOGGING_CONFIG = None  to 
settings,py

im running Python 2.7.5+, Django 1.6.2

couldn't find any info on how to fix this issue
all i know is, its something to do with logging module

anyone got any advice?





-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/b4ec8136-7394-43bd-a347-1f8b0b385ab1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


submit buttons in django

2014-03-19 Thread Harjot Mann
I have a form in my app and after entering data into that form I
submit that form but I want an another submit button like "Submit and
Add Event", so that after clicking on it it can redirect to an another
form. Please help me that how can I do this?

-- 
Harjot Kaur Mann
Blog: http://harjotmann.wordpress.com/
Daily Dairy: http://harjotmann.wordpress.com/daily-diary/

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAB0GQhBN_k%3Db8NHf8L4oZ1EWr-uya%3DhbotCZPGNam6ezy77vAg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Foreign key attribute in django

2014-03-19 Thread Harjot Mann
I have a field in my form that is related with foreign key to another
form and when I am filling a form that is required field but sometimes
I need to leave it blaink, how can I do this?

-- 
Harjot Kaur Mann
Blog: http://harjotmann.wordpress.com/
Daily Dairy: http://harjotmann.wordpress.com/daily-diary/

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAB0GQhCYWG3L%3DEGYWpi7quHY4TPA925qhg-Z%3Db9KO%2Bb9Jit1kw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: installing django trunk

2014-03-19 Thread Malik Rumi
Anybody? A little help here?
Just to update, I ran a search for 'migrations' in my django folder, and
got a lot of hits, but when I tried to actually run 'makemigrations" I got
'unknown command'


On Sat, Mar 15, 2014 at 6:37 PM, Malik Rumi  wrote:

> First, Dan, thanks for the reply. Second, apologies for the long delay,
> but sometimes the day job gets in the way. Third, I did as you suggested,
> but Django 1.6.1 was NOT removed. My best guess is that the official
> documentation instruction that pip would take care of this for me only
> applies when going from one official release to another, not when going
> from an official release to a development release, though of course it does
> not say so explicitly.
> pip did uninstall the 1.7 files from Python27/Scripts when I pointed it to
> them directly. I should add at this point that at the time of my original
> post, I did not realize that there were only 4 of them and that
> django-trunk was in the intended virtualenv alongside 1.6.1.
>
> However, pip would not only not uninstall django-trunk, it told me it
> wasn't installed, never mind the folder sitting there. Even better, git
> remove didn't work either. "Fatal: not a git repository"
>
> So I deleted django-trunk the old fashioned way, through my OS. Then I
> activated the virtualenv, reconnected to git, and got django-trunk and the
> admin files where I expected them to be - in the virtualenv. When I saw
> this in my terminal window:
>
>  Adding Django 1.7a2 to easy-install.pth file
> Deleting C:\Envs\VE1\Scripts\django-admin.py
> Installing django-admin-script.py script to C:\Envs\VE1\Scripts
>
> I assumed that meant it was taking care of 1.6.1 at the same time it was
> installing 1.7a2, as I understood the install instructions to say it would
> do. But when I ran print(django.get_version()), I got 1.6.1!
>
> Then I deleted both the django folder and the egg folder through Windows,
> but when I ran get_version again, I STILL got 1.6.1! I don't see how that
> is possible. There is another Django 1.6.1, but it is inside a DIFFERENT
> virtualenv, and when I exited the Python interpreter, I was right back to
> the VE I was working with. There is a django-admin in Python27, but when I
> opened it, it explicitly said that it was 1.7a2! Now it also had a line of
> code I didn't understand:
>
> require('Django==1.7a2')
> del require
>
> What is this doing? Deleting a requirement as soon as it is created? I
> don't understand.
>
> Finally, I decided to runserver. The good news is that my site still works
> as it did before. The bad news is I have no idea how or why. Runserver also
> explicitly stated that it was running 1.6.1.
>
> So, I guess I'll have to muddle along without migrations, which was the
> whole point of this exercise in futility. But I sure would like to
> understand what is happening here, if any of you wiser and more experienced
> heads can enlighten me.
>
>
>
> \
> On Saturday, March 8, 2014 3:10:20 AM UTC-6, Malik Rumi wrote:
>>
>> I am going from 1.6.1 to 1.7a2, mostly to take advantage of the new
>> migrations feature.
>> I followed the directions here http://django.readthedocs.org/en/latest/
>> topics/install.html#removing-old-versions-of-django
>> Since I originally installed with pip, supposedly that would take care of
>> removing the old version for me if I installed with pip now.
>> I changed into the subdirectory where 1.6.1 is, which is inside
>> virtualenvwrapper.
>> The commands they gave ran and reported success. However, 1.7a2 has been
>> installed at Python27/Scripts, not inside my virtualenv
>> 1.6.1 seems to alive and well at its same original location.
>> What do I now? Can I just delete the 1.6.1 folder? Will pip/virtualenv
>> know where to find 1.7a2 for my cuurent projects? Should I start the
>> install over?
>> Thx.
>>
>  --
> You received this message because you are subscribed to a topic in the
> Google Groups "Django users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/django-users/VnATClf-Wco/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/64ea91d3-f4df-470d-bad2-9c818708cb3c%40googlegroups.com
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http: