Ok, that was it, being completely unfamiliar with the Mac Terminal, I was
in the wrong directory. I navigated to the proper directory and got it
installed. Thanks for the help guys!
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe
Are you in the same directory as Django-1.5.1.tar.gz?
_Nik
On 4/15/2013 1:47 PM, Nathan Hall wrote:
> I've never used pip or virtualenv.
>
> When I did this: tar xzvf Django-1.5.1.tar.gz
>
> I got this:
> tar: Error opening archive: Failed to open 'Django-1.5.1.tar.gz'
>
>
>
> On Mon, Apr 15, 201
On Mon, Apr 15, 2013 at 2:47 PM, Nathan Hall wrote:
> I've never used pip or virtualenv.
>
> When I did this: tar xzvf Django-1.5.1.tar.gz
>
> I got this:
> tar: Error opening archive: Failed to open 'Django-1.5.1.tar.gz'
Then either you're not in the directory it was downloaded to
(typically ~/D
I've never used pip or virtualenv.
When I did this: tar xzvf Django-1.5.1.tar.gz
I got this:
tar: Error opening archive: Failed to open 'Django-1.5.1.tar.gz'
On Mon, Apr 15, 2013 at 4:40 PM, Avraham Serour wrote:
> doesn't pip and virtualenv work on mac?
>
>
> On Mon, Apr 15, 2013 at 11:37 P
doesn't pip and virtualenv work on mac?
On Mon, Apr 15, 2013 at 11:37 PM, Larry Martell wrote:
> On Mon, Apr 15, 2013 at 2:34 PM, Nathan Hall wrote:
> > Yep, I've got admin access, it's my personal machine.
> >
> > Actually, I looked again and it may not have been a password issue, this
> was
>
On Mon, Apr 15, 2013 at 2:34 PM, Nathan Hall wrote:
> Yep, I've got admin access, it's my personal machine.
>
> Actually, I looked again and it may not have been a password issue, this was
> the message I received: "python: can't open file 'setup.py': [Errno 2] No
> such file or directory"
Then y
Yep, I've got admin access, it's my personal machine.
Actually, I looked again and it may not have been a password issue, this
was the message I received: "python: can't open file 'setup.py': [Errno 2]
No such file or directory"
On Mon, Apr 15, 2013 at 4:29 PM, Larry Martell wrote:
> On Mon, Apr
On Mon, Apr 15, 2013 at 2:24 PM, Nathan Hall wrote:
> I tried my password, it doesn't work.
Go to System Preferences, Users and Groups. Is your account an Admin
account? If not, you can't sudo. You'll need someone with an admin
account to install it for you. But if you don't have an admin account
I tried my password, it doesn't 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 emai
On Mon, Apr 15, 2013 at 2:02 PM, Nathan Hall wrote:
>
> Yep, I'm on 10.8.3. I tried sudo python setup.py install and it asked for
> a password. I assumed it was just looking for my system password but that
> didn't work.
It's asking for your own password.
--
You received this message because yo
Yep, I'm on 10.8.3. I tried sudo python setup.py install and it asked for a
password. I assumed it was just looking for my system password but that
didn't work.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and s
This is likely the cause of the problem. You should always install
packages with setup.py (as mentioned by the previous poster). I've found
Mac OS X to have lots of "false" site-packages folders. setup.py will
make sure it gets to the correct one. Also some packages may have extra
installation step
On Mon, Apr 15, 2013 at 12:40 PM, Starboy wrote:
> Hi all,
>
> Totally new to django and just trying to get it installed but I keep getting
> the "ImportError: No module named django" error. I've searched around quite
> a bit looking for the answer to my problem but nothing seems to work.
>
> I'm
Hi,
You mentioned that you installed BitNami DjangoStack. For using it you
should first go to the Windows Start Menu and click in the 'Use
DjangoStack" link. Then you can execute python and 'import django'
should work. You also have Python 2.7 installed so if you don't load
the BitNami environment
Hi,
Also, If you haven't read ALL of this yet
http://docs.python.org/tutorial/index.html go ahead and do so.
On Sat, Nov 19, 2011 at 2:29 PM, Jenny wrote:
> Thank you Furbee. I will try later to to put the unpacked Django in
> the same folder as setup.py folder. I'll be back soon with the
> re
Thank you Furbee. I will try later to to put the unpacked Django in
the same folder as setup.py folder. I'll be back soon with the
result.
On 18 Nov, 23:02, Furbee wrote:
> You can get to the python interactive interpreter by typing "python" into a
> Dos shell, as long as the python executable is
You can get to the python interactive interpreter by typing "python" into a
Dos shell, as long as the python executable is in your system path. The
IDLE command line should work, also. In the Python folder there should be a
site-packages folder which contains a folder named django. The "import
djan
Hello Tim,
I'm a fellow Mac user but I don't quite understand the problem that you are
having installing Django on OS X 10.6.
I installed Django today on a new Mac and it took all of 5 minutes and I
downloaded the tarball, extracted it and threw it in my home directory.
I believe that 10.6 comes
On 03/03/2010 07:27 PM, Tim Jones wrote:
So I tried specifying the site-packages path at the top of my script
and it removed the ImportError. That makes it seem like my
web-server's pythong is running with different pythonpath settings
than my command-line's python. I think I can probably unravel
Sorry, I should clarify.
When I wrote:
> So I tried specifying the site-packages path at the top of my script...
I meant that I added these lines:
~~
import sys
sys.path.insert(0, "/opt/local/lib/python2.5/site-packages")
~~
=T=
--
You received this message because you are subscribed to the G
Aha, that is helpful. I think I've partially solved this now.
If I run 'import django' at the command line, then it seems to import fine;
there is no error message, and 'print sys.modules' now lists it.
So I tried specifying the site-packages path at the top of my script and it
removed the Impo
Printing sys.modules won't show django unless you've imported Django.
What are you trying to do, anyway? You don't normally import Django in a Python
script. You usually start a Django project by using django-admin.py and letting
it create a manage.py which uses the proper Python.
Search your s
Thanks for the reply.
"which python" returns: /opt/local/bin/python
"python -V" returns: Python 2.5.5
I know I've got the OSX default Pythons installed as well, but I've done my
best to avoid running those.
Like I said in my first email, printing sys.path in the python prompt returns a
big li
Please post the results of these commands:
which python
python -V
You can have different versions of Python installed (or even the same version)
in multiple places on your Mac. The most likely situation is that when you're
trying to actually run things you're using different version of Pyth
I attempted installation via tarball instead of MacPorts. This had no
effect on things. Same files in the same places, same error.
=T=
On Mar 3, 11:15 am, Tones wrote:
> Hi --
>
> I'm attempting to run Django on OSX 10.6. I've installed Python2.5 and
> Py25-Django (Django v1.1) via MacPorts.
Great!
and I just want to say thank you to everyone that helped me with this
problem, it is very much appreciated.
On Jul 9, 6:03 pm, "Peter Herndon" <[EMAIL PROTECTED]> wrote:
> Yes, the install worked. If you can import a module without error,
> it's installed successfully.
>
> Mostly. ;) Yo
Yes, the install worked. If you can import a module without error,
it's installed successfully.
Mostly. ;) You can also successfully import a module even if it is
not on PYTHON_PATH, if you are in the same directory as the module.
---Peter Herndon
On 7/9/08, MadMax007 <[EMAIL PROTECTED]> wro
Thanks for the links I'll check them out
One last question, I re-did the installation for Django using some
instructions I found on Google. When I open Python now and type:
>>> import.django
>>> django.VERSION
>>> (0,96 ) "There's something else after the 0, 96 but I can't remember what
>>> it
Apparently Django is not present in the PYTHONPATH and therefore not
reachable by Python.
I'm not a Mac user, but some help can be found on google.
Try there for example:
http://antoniocangiano.com/2007/12/22/how-to-install-django-with-mysql-on-mac-os-x/
http://www.rhonabwy.com/wp/2006/07/20/inst
Ok, for the PYTHONPATH I got:
>>> import sys
>>> print sys.path
['', '/System/Library/Frameworks/Python.framework/Versions/2.5/lib/
python25.zip', '/System/Library/Frameworks/Python.framework/Versions/
2.5/lib/python2.5', '/System/Library/Frameworks/Python.framework/
Versions/2.5/lib/python2.5/pl
Hi,
This means that Django is not in the PYTHONPATH. To check what's in
that path, run the following in Python:
>>> import sys
>>> print sys.path
On Jul 9, 9:35 am, Juanjo Conti <[EMAIL PROTECTED]> wrote:
> How did you exactly install it?
> Which folders are in your PYTHONPATH?
>
> Juanjo
> --
How did you exactly install it?
Which folders are in your PYTHONPATH?
Juanjo
--
mi blog: http://www.juanjoconti.com.ar
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, se
@Graham:
It looks like it is a working django load. Also, the permissions are
the same as when they were able to load while in the python site
packages folder.
---
Python 2.4.3 (#1, Dec 11 2006, 11:38:52)
[GCC 4.1.1 20061130 (Red Hat 4.1.1-43)] on linux2
Type "help", "copyright", "cred
On Jan 15, 2008 9:48 PM, Scott <[EMAIL PROTECTED]> wrote:
> /Working/django
Out of curiosity, what are the contents of this directory? Is this the
root of the django distribution (containing things like 'docs',
'tests' and another 'django' directory), or is this the django code
itself (containing
On Jan 15, 2008 6:55 PM, Scott <[EMAIL PROTECTED]> wrote:
> MY SYSTEM:
>
> OS = { Red Hat Enterprise Linux 5 | RHEL 5 | RHEL5 }
> Python 2.4.3 (#1, Dec 11 2006, 11:38:52)
> Apache/2.2.3 (Red Hat) Server
> mod_python.version '3.2.8'
> Django VERSION = (0, 97, 'pre')
>
>From all the information you
First verify Django is being picked up from where you think it is by
doing:
import django
print django.__file__
Second, ensure that the installed Django files have permissions that
would allow user that Apache may be running as to access it. That is,
if Apache is running as a service and the
1234,
Yes, with these directives:
SetHandler python-program
PythonPath "['/Working/django','/Working/modules','/Working/
projects','/Working/projects/mysite'] + sys.path"
SetEnv DJANGO_SETTINGS_MODULE mysite.settings
PythonHandler mod_python.testhandler
#PythonH
django is in your sys.path?
2008/1/16, Scott <[EMAIL PROTECTED]>:
>
>
> Thank you to anyone who may be of help...
>
> PROBLEM:
>
> ImportError: No module named django
>
> MY SETTINGS:
>
> /Working/django/django/__init__.py (file exists)
> /Working/projects/ (my main
Ok, I took the last email private with Rob, and got it sorted! It
seemed that apache couldn't access any files in /home/acid2, so the
solution has been to move everything into /opt/django, so I did:
sudo mv /home/acid2/src/django_src/ /opt/django/src/
sudo rm /usr/lib/python2.4/site-packages/djan
maybe apache or apache mod_python is set not to follow symlinks. copy
the django code into site-packages (not merely a symlink) and try if
that works.
On Apr 18, 11:10 pm, Oliver Charles <[EMAIL PROTECTED]> wrote:
> I get...
>
> [EMAIL PROTECTED] ~]$ sudo -u apache python
> Password:
> Python 2.4
Okay, you're getting much closer. Try 'sudo -u apache ls -l /usr/lib/
python2.4/site-packages/' and 'site-packages/django' to look at
permissions.
On Apr 18, 2:10 pm, Oliver Charles <[EMAIL PROTECTED]> wrote:
> I get...
>
> [EMAIL PROTECTED] ~]$ sudo -u apache python
> Password:
> Python 2.4.3 (#
I get...
[EMAIL PROTECTED] ~]$ sudo -u apache python
Password:
Python 2.4.3 (#1, Mar 14 2007, 18:51:08)
[GCC 4.1.1 20070105 (Red Hat 4.1.1-52)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import django
Traceback (most recent call last):
File "", line 1,
What happens when you run:
sudo -u apache python
>>> import django
>>> django
BTW, I use openhosting and have a few django sites running so don't be
discouraged!
-rob
On Apr 18, 12:59 pm, Oliver Charles <[EMAIL PROTECTED]> wrote:
> Ok,
>
> I've done a ton of googling on this, and not come up
On Mon, 2006-07-17 at 18:58 -0700, markguy wrote:
> I've got my output at least resembling yours now, thanks to your
> explanation about the difference between URL config and apps.
>
> I'm using this for urlpatterns:
> ( r'^$' , 'django.views.generic.simple.direct_to_template' , {
> 'template' :
Okay, ./manage.py syncdb before ./manage.py sql goods is apparently a
good idea.
So, I've now got a very basic index page loading up as expected.
I'm off for a couple drinks to see if I can wrap my head around how
Django compartmentalizes things and then will endeavor to not bring
many more prob
I've got my output at least resembling yours now, thanks to your
explanation about the difference between URL config and apps.
I'm using this for urlpatterns:
( r'^$' , 'django.views.generic.simple.direct_to_template' , {
'template' : 'index.html' } ) ,
However, there's a new wrinkle. While tryi
That fixed that particular issue. My unfamiliarity with Python lists
betrayed me there.
--~--~-~--~~~---~--~~
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@googleg
On Mon, 2006-07-17 at 08:22 -0700, markguy wrote:
> Changing bbg.goods to bbg.goods.url throws the same exception as
> bbg.goods.
So inside your project directory, try something like the following (I am
pasting a terminal session using one of my own projects just to show
what sort of output I see
On Mon, 2006-07-17 at 07:34 -0700, markguy wrote:
>
> Malcolm Tredinnick wrote:
>
> > That should be easy enough to diagnose. My initial guess would be that
> > bbg is in django_projects/, rather than django_src/, just from the way
> > you named your directories. Remember that .bash_profile is o
On Mon, 2006-07-17 at 07:45 -0700, markguy wrote:
> So, what you were *really* suggesting was that PYTHONPATH should
> include the project directory, not the django_src directory? I saw that
> while skimming through the docs.
>
> I changed PYTHONPATH to reflect that (apparently, adding both
> dir
Changing bbg.goods to bbg.goods.url throws the same exception as
bbg.goods.
--~--~-~--~~~---~--~~
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
So, what you were *really* suggesting was that PYTHONPATH should
include the project directory, not the django_src directory? I saw that
while skimming through the docs.
I changed PYTHONPATH to reflect that (apparently, adding both
directories in a fit of crankiness doesn't help matters):
Python
Malcolm Tredinnick wrote:
> That should be easy enough to diagnose. My initial guess would be that
> bbg is in django_projects/, rather than django_src/, just from the way
> you named your directories. Remember that .bash_profile is obviously not
> going to be run by Apache (it's not bash, after
On Mon, 2006-07-17 at 04:43 -0700, markguy wrote:
> I'm covering all the bases. Or trying to.
>
> re: django_source: Wow. Uh, thanks. I have no idea why I typed that out
> fully in httpd.conf. Fixing that leads to a new error:
>
> EnvironmentError: Could not import settings 'bbg.settings' (Is it
I'm covering all the bases. Or trying to.
re: django_source: Wow. Uh, thanks. I have no idea why I typed that out
fully in httpd.conf. Fixing that leads to a new error:
EnvironmentError: Could not import settings 'bbg.settings' (Is it on
sys.path? Does it have syntax errors?): No module named bb
On Mon, 2006-07-17 at 03:57 -0700, markguy wrote:
> I have poked around looking for an answer to this and none of the
> suggestions/fixes I found did the trick.
>
> Ubuntu 6.06/Python
> 2.4.3/Apache2.0.55/mod_python3.1.4/mySQL5.0.22/Django0.95
>
> Relevant bits to follow
> httpd.conf:
>
>
On 6/30/06, Craig Marshall <[EMAIL PROTECTED]> wrote:
> I can
> import django at the python prompt, but running syncdb gives me the
> ImportError.
What does python -v manage.py yield? 't Will be a long output.
Probably best to put it up on a URL if you can.
--
Jeroen Ruigrok van der Werven
--~
> I'd advise you to drop the symlink and use the PYTHONPATH variable,
> but that's just my hunch based on no empirical data.
Okay, I just deleted /usr/lib/python2.4/site-packages/django (which
was the symlink), and added to the PYTHONPATH environment variable the
actual django directory, and if f
On 6/30/06, Craig Marshall <[EMAIL PROTECTED]> wrote:
> Only the symlink I made called "django" which points to the actual
> django dir in my $HOME
I'd advise you to drop the symlink and use the PYTHONPATH variable,
but that's just my hunch based on no empirical data.
--
Jeroen Ruigrok van der
> This is very strangely worded. You installed Ubuntu completely on top
> of Debian and then installed Django from SVN again? You're not being
> explicit enough.
Sorry for being unclear. I had debian sarge installed, and I installed
django from svn at that point. Then I wiped my machine entirely,
On 6/28/06, Craig Marshall <[EMAIL PROTECTED]> wrote:
> I downloaded the svn version of django a couple of weeks ago, and had
> it working fine within Debian. I installed Ubuntu 6.06 today, and my
> django install has stopped working.
This is very strangely worded. You installed Ubuntu completely
> I downloaded the svn version of django a couple of weeks ago, and had
> it working fine within Debian. I installed Ubuntu 6.06 today, and my
> django install has stopped working.
>
> I can run python interactively and type "import django" and get no
> errors, but when I go into our project direc
> It sounds like you might have two versions of Python installed. You
> should confirm that the shebang line in ./manage.py is for the right
> version. Alternatively, running 'python manage.py syncdb' should work.
The shebang says "#!/usr/bin/env python", which returns 2.4.3 when
asked. (So does
On 28 Jun 2006, at 14:39, Craig Marshall wrote:
> I can run python interactively and type "import django" and get no
> errors, but when I go into our project directory and run "./manage.py
> syncdb", I get this error:
>
> ImportError: No module named django
>
> I'm running Python 2.4.3 in case t
64 matches
Mail list logo
