Installing Django

[Frederick Miller]

For Windows XP, should Django be installed under the Python27 folder?  Or should Django be on the root of the C: drive?

 

Frederick Miller

[Thomas Lockhart]

On 12/12/13 1:55 PM, Frederick Miller wrote:
> For Windows XP, should Django be installed under the Python27 folder?
> Or should Django be on the root of the C: drive?

I have no experience with Windows installations, but for other platforms
virtualenv and pip are a real help for getting repeatable, consistent
installations with a minimum of effort. I believe that is the case for
Windows boxes too.

If you use virtualenv, then you will have a complete python and django
installation in a location of your choosing, independent of the system
installation areas.

hth

- Tom

> Frederick Miller
> --
> 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...@googlegroups.com.
> To post to this group, send email to django...@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/303094d2-2a45-4c56-bcf8-4884e97be365%40googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

[Anurag Chourasia]

It goes into Lib\site-packages folder.

Regards,

Anurag

On Thu, Dec 12, 2013 at 6:55 PM, Frederick Miller <fjmil...@gmail.com> wrote:

For Windows XP, should Django be installed under the Python27 folder?  Or should Django be on the root of the C: drive?

 

Frederick Miller

--

[Mike Dewhirst]

Frederick

On Windows, the easiest (decision-less) way to install Django is using pip or easy-install. Get pip first if you haven't done so already. Django will then end up in exactly the right place and work faultlessly. I recommend it.

Virtualenv becomes important when you want to run multiple separate Python projects (such as Django projects) but it is a complication you can do without if you are just starting. For example, you might have different projects which absolutely require different versions of (say) Python while you are migrating a project from Python 2.7 to 3.x. Or you might be committed to maintaining multiple versions of the same software and they have different 3rd party app requirements between versions.

VirtualenvWrapper makes manipulating Virtualenv easier but it doesn't appear to be available for Windows.

So, Django will end up in the right place if you use pip. If you install Virtualenv and activate it *then* use pip to install Django, it will also end up in the right place but only for the activated (virtual) environment. This is how you can install different versions of software in different virtual environments.

The real answer to your question is "you shouldn't care".

Mike

[mulianto]

Frederick,

Python installer on windows by default install in c:\python 2.x\

And all package like django and others will be under python folder install in libs\site-package\

Better look to use virtenv so you can create a different environment for different project.

Thanks

Mulianto

Blog - Http://muliantophang.blogspot.com

Sent from my iPhone

--

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...@googlegroups.com.
To post to this group, send email to django...@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/3a5619ca-f314-4229-bd97-030b054118d7%40googlegroups.com.

[Frederick Miller]

Thank you, Mulianto.

[Frederick Miller]

Thank you, Mike.

[Frederick Miller]

Thank you, Guddu.

[Frederick Miller]

Thank you, Thomas.