outdated django book

2012-04-27 Thread knowledge_seeker
My Django book (from the university library) said to add the label
"@login_required" to views that I wish to restrict user access on.
Django 1.4 does not allow this; obviously the book is dated! Is there
a more modern way to get the same effect?

Similarly, admin does not allow access to my classes, even when I have
created an Admin class; is this a new security feature?

Finally, when I tried to create a view that allowed web-based user
creation, the views.py file would not recognize the class "User"; is
there something I need to import?

-- 
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: outdated django book

2012-04-29 Thread knowledge_seeker
Thanks for the help guys; I am glad the books were not so out of date!

On Friday, April 27, 2012 7:09:32 PM UTC-7, knowledge_seeker wrote:
>
> My Django book (from the university library) said to add the label 
> "@login_required" to views that I wish to restrict user access on. 
> Django 1.4 does not allow this; obviously the book is dated! Is there 
> a more modern way to get the same effect? 
>
> Similarly, admin does not allow access to my classes, even when I have 
> created an Admin class; is this a new security feature? 
>
> Finally, when I tried to create a view that allowed web-based user 
> creation, the views.py file would not recognize the class "User"; is 
> there something I need to import?


On Friday, April 27, 2012 7:09:32 PM UTC-7, knowledge_seeker wrote:
>
> My Django book (from the university library) said to add the label 
> "@login_required" to views that I wish to restrict user access on. 
> Django 1.4 does not allow this; obviously the book is dated! Is there 
> a more modern way to get the same effect? 
>
> Similarly, admin does not allow access to my classes, even when I have 
> created an Admin class; is this a new security feature? 
>
> Finally, when I tried to create a view that allowed web-based user 
> creation, the views.py file would not recognize the class "User"; is 
> there something I need to import?

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-users/-/nV5rR7liHNYJ.
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: Help - Which IDE is best to use.

2012-05-15 Thread knowledge_seeker
For people used to using Vim in Unix, there is an Eclipse plug-in called 
Vwrapper.

- knowledge_seeker

On Tuesday, May 15, 2012 3:16:00 AM UTC-7, Karl Sutt wrote:
>
> I use Vim, for everything involving writing -- coding, producing 
> papers/articles/reports, editing existing code and documents. It is not an 
> IDE, but a text editor, and it is absolutely excellent. Once you learn Vim, 
> you'll never want to use anything else (this is the case for me, at least). 
> The learning curve is rather steep, but after you get used to the different 
> modes, moving around and editing text efficiently, you start to see and 
> appreciate the power of the keyboard.
>
> The downside is that it does not come with documentation built in, or the 
> code-checking and all that fancy stuff, like the bigger counterparts 
> (Eclipse, Aptana, pyCharm etc), but I personally don't need it.
> The upside is that you are not tied to a specific IDE for a specific 
> language/framework. Vim lets you edit code and text efficiently, regardless 
> of what language/framework/task you are working with.
>
> Obviously, my goal is not to say Vim (another example is GNU Emacs) is the 
> best editor ever, but to let people know of tools that have been around 
> since the beginning of first operating systems. They have been perfected 
> over the past 20 years by professionals, people who wrote the very 
> operating systems you use today.
>
> For a beginner programmer, my suggestion is to always start with the 
> simplest tools possible, and not let one IDE do everything for you, without 
> you understanding the process. The downside is that you'll have to put in a 
> lot more effort to get going and you don't get the fancy add-ons. But the 
> upside (in my opinion, anyway) is that you gain a deeper understanding of 
> how these things fit together, giving you a better insight into whatever 
> you're working on. Don't be afraid to get your hands dirty :-)
>
> Karl Sutt
>
>
> On Tue, May 15, 2012 at 10:51 AM, cougar cougar wrote:
>
>> ulipad , free  and build with wxpython
>>
>>
>> 2012/5/14 Sanjay M 
>>
>>> I am new to Django, and I was confused in choosing a IDE between Eclipse 
>>> and aptana studio 3 to edit source code. Kindly suggest me a good one. 
>>>
>>> Thank you in advance,
>>> Regards,
>>> Sanjay M
>>>
>>>
>>>  -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Django users" group.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msg/django-users/-/2LIdVrSuFpQJ.
>>> 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.
>>>
>>
>>  -- 
>> 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.
>>
>
>
On Tuesday, May 15, 2012 3:16:00 AM UTC-7, Karl Sutt wrote:
>
> I use Vim, for everything involving writing -- coding, producing 
> papers/articles/reports, editing existing code and documents. It is not an 
> IDE, but a text editor, and it is absolutely excellent. Once you learn Vim, 
> you'll never want to use anything else (this is the case for me, at least). 
> The learning curve is rather steep, but after you get used to the different 
> modes, moving around and editing text efficiently, you start to see and 
> appreciate the power of the keyboard.
>
> The downside is that it does not come with documentation built in, or the 
> code-checking and all that fancy stuff, like the bigger counterparts 
> (Eclipse, Aptana, pyCharm etc), but I personally don't need it.
> The upside is that you are not tied to a specific IDE for a specific 
> language/framework. Vim lets you edit code and text efficiently, regardless 
> of what language/framework/task you are working with.
>
> Obviously, my goal is not to say Vim (another example is GNU Emacs) is the 
> best editor ever, but to let people know of tools that have been around 
> since the beginning of first operating systems. They have been perfected 
> over the past 20 years by professionals, people who wrote the very 
> operatin

python path in webpage error message not virtual environment's

2014-02-17 Thread knowledge_seeker
I understand the importance of doing projects in virtual environments, but 
I am hitting one snag. 

When I have an error in django, and I get the generated webpage with an 
error message, it shows the 'normal' python path, site packages installed, 
etc. For example, I have jinja on my main installation, but not in the 
virtual environment. Yet, jinja shows up in this message as one of the site 
packages; similarly with the other python packages. Is there any way to 
show the python version (and location) and correct site-packages that are 
in the virtual environment in these error messages?

-- 
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/59bfb435-e16f-47eb-90d2-55cc8ec02d0b%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.