hello everyone please can someone help me with my problem is very important please Environment: Request Method: GET Request URL: http://127.0.0.1:8000/user/ Django Version: 4.0.4 Python Version: 3

[ray nkamwa]

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/afc98569-1c64-4322-a533-d62a1a297115n%40googlegroups.com.
Environment:


Request Method: GET
Request URL: http://127.0.0.1:8000/user/

Django Version: 4.0.4
Python Version: 3.10.4
Installed Applications:
['django.contrib.admin',
 'django.contrib.auth',
 'django.contrib.contenttypes',
 'django.contrib.sessions',
 'django.contrib.messages',
 'django.contrib.staticfiles',
 'djangopressing',
 'bdpressing',
 'rest_framework',
 'django_filters',
 'rest_framework.authtoken',
 'dj_rest_auth']
Installed Middleware:
['django.middleware.security.SecurityMiddleware',
 'django.contrib.sessions.middleware.SessionMiddleware',
 'django.middleware.common.CommonMiddleware',
 'django.middleware.csrf.CsrfViewMiddleware',
 'django.contrib.auth.middleware.AuthenticationMiddleware',
 'django.contrib.messages.middleware.MessageMiddleware',
 'django.middleware.clickjacking.XFrameOptionsMiddleware']



Traceback (most recent call last):
  File 
"C:\Users\User\Desktop\djangopressing\env\lib\site-packages\django\core\handlers\exception.py",
 line 55, in inner
response = get_response(request)
  File 
"C:\Users\User\Desktop\djangopressing\env\lib\site-packages\django\core\handlers\base.py",
 line 197, in _get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File 
"C:\Users\User\Desktop\djangopressing\env\lib\site-packages\django\views\decorators\csrf.py",
 line 54, in wrapped_view
return view_func(*args, **kwargs)
  File 
"C:\Users\User\Desktop\djangopressing\env\lib\site-packages\rest_framework\viewsets.py",
 line 125, in view
return self.dispatch(request, *args, **kwargs)
  File 
"C:\Users\User\Desktop\djangopressing\env\lib\site-packages\rest_framework\views.py",
 line 509, in dispatch
response = self.handle_exception(exc)
  File 
"C:\Users\User\Desktop\djangopressing\env\lib\site-packages\rest_framework\views.py",
 line 469, in handle_exception
self.raise_uncaught_exception(exc)
  File 
"C:\Users\User\Desktop\djangopressing\env\lib\site-packages\rest_framework\views.py",
 line 480, in raise_uncaught_exception
raise exc
  File 
"C:\Users\User\Desktop\djangopressing\env\lib\site-packages\rest_framework\views.py",
 line 497, in dispatch
self.initial(request, *args, **kwargs)
  File 
"C:\Users\User\Desktop\djangopressing\env\lib\site-packages\rest_framework\views.py",
 line 415, in initial
self.check_permissions(request)
  File 
"C:\Users\User\Desktop\djangopressing\env\lib\site-packages\rest_framework\views.py",
 line 331, in check_permissions
for permission in self.get_permissions():
  File 
"C:\Users\User\Desktop\djangopressing\env\lib\site-packages\rest_framework\views.py",
 line 278, in get_permissions
return [permission() for permission in self.permission_classes]

Exception Type: TypeError at /user/
Exception Value: 'BasePermissionMetaclass' object is not iterable

Re: regarding virtualenv and python version 3.5 or 3.4 or other versions

[Seo Brain]

pyenv - github way - it works for me.
thanks.

On Wednesday, August 16, 2017 at 2:18:08 AM UTC-7, Avraham Serour wrote:
>
> on the same link it is mentioned "To not touch the system Python 
> (generally a bad idea..."
>
> it is suggested to use pyenv, you may use instead pythonz
>
> On Wed, Aug 16, 2017 at 3:56 AM, Seo Brain 
> > wrote:
>
>> Hi Avraham
>>
>> Thanks.
>>
>> I did install the python V3.6 on my dev-server ubuntu 14.04 
>>
>> by using this
>>
>> https://askubuntu.com/questions/865554/how-do-i-install-python-3-6-using-apt-get
>>
>> //also map 3.6.2 to python3 folder by this way
>> sudo rm python3 
>> sudo ln -s python3.5 python3 
>>
>> python -V shows v3.6.2
>> sudo apt-get install python3.6-venv -- able to install virtualenv
>>
>> and python -V is v2.7 and python3 -V is v3.6.2  
>>
>> which python3 -- (/usr/bin/python3)
>>
>> which pip3 (/usr/local/bin/pip3) or pip (/usr/local/bin/pip) display the 
>> path 
>>
>> and issue is pip -V or pip3 -V , error display
>>
>> 
>> Traceback (most recent call last):
>>   File "/usr/local/bin/pip3", line 7, in 
>> from pip import main
>>   File "/usr/lib/python3/dist-packages/pip/__init__.py", line 59, in 
>> 
>> from pip.log import logger
>>   File "/usr/lib/python3/dist-packages/pip/log.py", line 9, in 
>> import colorama, pkg_resources
>>   File "", line 961, in _find_and_load
>>   File "", line 950, in 
>> _find_and_load_unlocked
>>   File "", line 646, in _load_unlocked
>>   File "", line 616, in 
>> _load_backward_compatible
>>   File 
>> "/usr/share/python-wheels/setuptools-3.3-py2.py3-none-any.whl/pkg_resources.py",
>>  
>> line 1479, in 
>> register_loader_type(importlib_bootstrap.SourceFileLoader, 
>> DefaultProvider)
>> AttributeError: module 'importlib._bootstrap' has no attribute 
>> 'SourceFileLoader'
>> ---
>>
>>
>> and i tried to upgrade the pip3 and still the same error.
>>
>> Please help to figure it out.
>>
>> Thanks
>>
>> Ross
>>
>>
>>
>> On Sunday, August 13, 2017 at 8:11:57 AM UTC-7, Avraham Serour wrote:
>>>
>>> I suggest using 3.6, which is the current stable release
>>> if your machine or the server doesn't have this version installed you 
>>> may compile it yourself and create the virtualenv for the project from there
>>>
>>> There are some projects that help you with that, I like pythonz 
>>> https://github.com/saghul/pythonz
>>>
>>>
>>> On Sun, Aug 13, 2017 at 9:33 AM, Seo Brain  wrote:
>>>
>>>> Hi, the question is about which python version suppose to use. On web 
>>>> server is ubuntu 14.4 - python v3.4 (i assume) with virtualenv, my local 
>>>> is 
>>>> python v3.5 or may be using v3.4 if i have to keep the same version on web 
>>>> server ? v3.4 seems has issue to install on one of my windows 7, but no 
>>>> issue on mac. or may be i suppose to use virtual-box to keep the 
>>>> environment same everywhere dev and production server ?
>>>> thanks in advance. Ross
>>>>
>>>> -- 
>>>> 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 https://groups.google.com/group/django-users.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/django-users/7937063c-e3cb-44b7-b524-097b82d05d87%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/django-users/7937063c-e3cb-44b7-b524-097b82d05d87%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>> 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...@googlegroups.com .
>> To post to this group, send email to django...@googlegroups.com 
>> .
&g

Re: regarding virtualenv and python version 3.5 or 3.4 or other versions

[Avraham Serour]

on the same link it is mentioned "To not touch the system Python (generally
a bad idea..."

it is suggested to use pyenv, you may use instead pythonz

On Wed, Aug 16, 2017 at 3:56 AM, Seo Brain  wrote:

> Hi Avraham
>
> Thanks.
>
> I did install the python V3.6 on my dev-server ubuntu 14.04
>
> by using this
> https://askubuntu.com/questions/865554/how-do-i-
> install-python-3-6-using-apt-get
>
> //also map 3.6.2 to python3 folder by this way
> sudo rm python3
> sudo ln -s python3.5 python3
>
> python -V shows v3.6.2
> sudo apt-get install python3.6-venv -- able to install virtualenv
>
> and python -V is v2.7 and python3 -V is v3.6.2
>
> which python3 -- (/usr/bin/python3)
>
> which pip3 (/usr/local/bin/pip3) or pip (/usr/local/bin/pip) display the
> path
>
> and issue is pip -V or pip3 -V , error display
>
> 
> Traceback (most recent call last):
>   File "/usr/local/bin/pip3", line 7, in 
> from pip import main
>   File "/usr/lib/python3/dist-packages/pip/__init__.py", line 59, in
> 
> from pip.log import logger
>   File "/usr/lib/python3/dist-packages/pip/log.py", line 9, in 
> import colorama, pkg_resources
>   File "", line 961, in _find_and_load
>   File "", line 950, in
> _find_and_load_unlocked
>   File "", line 646, in _load_unlocked
>   File "", line 616, in
> _load_backward_compatible
>   File 
> "/usr/share/python-wheels/setuptools-3.3-py2.py3-none-any.whl/pkg_resources.py",
> line 1479, in 
> register_loader_type(importlib_bootstrap.SourceFileLoader,
> DefaultProvider)
> AttributeError: module 'importlib._bootstrap' has no attribute
> 'SourceFileLoader'
> ---
>
>
> and i tried to upgrade the pip3 and still the same error.
>
> Please help to figure it out.
>
> Thanks
>
> Ross
>
>
>
> On Sunday, August 13, 2017 at 8:11:57 AM UTC-7, Avraham Serour wrote:
>>
>> I suggest using 3.6, which is the current stable release
>> if your machine or the server doesn't have this version installed you may
>> compile it yourself and create the virtualenv for the project from there
>>
>> There are some projects that help you with that, I like pythonz
>> https://github.com/saghul/pythonz
>>
>>
>> On Sun, Aug 13, 2017 at 9:33 AM, Seo Brain  wrote:
>>
>>> Hi, the question is about which python version suppose to use. On web
>>> server is ubuntu 14.4 - python v3.4 (i assume) with virtualenv, my local is
>>> python v3.5 or may be using v3.4 if i have to keep the same version on web
>>> server ? v3.4 seems has issue to install on one of my windows 7, but no
>>> issue on mac. or may be i suppose to use virtual-box to keep the
>>> environment same everywhere dev and production server ?
>>> thanks in advance. Ross
>>>
>>> --
>>> 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 https://groups.google.com/group/django-users.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/django-users/7937063c-e3cb-44b7-b524-097b82d05d87%40googlegroups.com
>>> <https://groups.google.com/d/msgid/django-users/7937063c-e3cb-44b7-b524-097b82d05d87%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> 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 https://groups.google.com/group/django-users.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/django-users/82d094db-0338-495b-963e-c912cf068171%40googlegroups.com
> <https://groups.google.com/d/msgid/django-users/82d094db-0338-495b-963e-c912cf068171%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> 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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAFWa6t%2B7HDffpaHxs%3DFvVU8z4sCJm7-dWZvqYRdFoEqd9jGXoA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: regarding virtualenv and python version 3.5 or 3.4 or other versions

[Seo Brain]

Hi Avraham

Thanks.

I did install the python V3.6 on my dev-server ubuntu 14.04 

by using this
https://askubuntu.com/questions/865554/how-do-i-install-python-3-6-using-apt-get

//also map 3.6.2 to python3 folder by this way
sudo rm python3 
sudo ln -s python3.5 python3 

python -V shows v3.6.2
sudo apt-get install python3.6-venv -- able to install virtualenv

and python -V is v2.7 and python3 -V is v3.6.2  

which python3 -- (/usr/bin/python3)

which pip3 (/usr/local/bin/pip3) or pip (/usr/local/bin/pip) display the 
path 

and issue is pip -V or pip3 -V , error display


Traceback (most recent call last):
  File "/usr/local/bin/pip3", line 7, in 
from pip import main
  File "/usr/lib/python3/dist-packages/pip/__init__.py", line 59, in 

from pip.log import logger
  File "/usr/lib/python3/dist-packages/pip/log.py", line 9, in 
import colorama, pkg_resources
  File "", line 961, in _find_and_load
  File "", line 950, in _find_and_load_unlocked
  File "", line 646, in _load_unlocked
  File "", line 616, in 
_load_backward_compatible
  File 
"/usr/share/python-wheels/setuptools-3.3-py2.py3-none-any.whl/pkg_resources.py",
 
line 1479, in 
register_loader_type(importlib_bootstrap.SourceFileLoader, 
DefaultProvider)
AttributeError: module 'importlib._bootstrap' has no attribute 
'SourceFileLoader'
---


and i tried to upgrade the pip3 and still the same error.

Please help to figure it out.

Thanks

Ross



On Sunday, August 13, 2017 at 8:11:57 AM UTC-7, Avraham Serour wrote:
>
> I suggest using 3.6, which is the current stable release
> if your machine or the server doesn't have this version installed you may 
> compile it yourself and create the virtualenv for the project from there
>
> There are some projects that help you with that, I like pythonz 
> https://github.com/saghul/pythonz
>
>
> On Sun, Aug 13, 2017 at 9:33 AM, Seo Brain 
> > wrote:
>
>> Hi, the question is about which python version suppose to use. On web 
>> server is ubuntu 14.4 - python v3.4 (i assume) with virtualenv, my local is 
>> python v3.5 or may be using v3.4 if i have to keep the same version on web 
>> server ? v3.4 seems has issue to install on one of my windows 7, but no 
>> issue on mac. or may be i suppose to use virtual-box to keep the 
>> environment same everywhere dev and production server ?
>> thanks in advance. Ross
>>
>> -- 
>> 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 https://groups.google.com/group/django-users.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/7937063c-e3cb-44b7-b524-097b82d05d87%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/django-users/7937063c-e3cb-44b7-b524-097b82d05d87%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> 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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/82d094db-0338-495b-963e-c912cf068171%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: regarding virtualenv and python version 3.5 or 3.4 or other versions

[Andréas Kühne]

If you want something to scale - make sure that you make the right
prerequisites for that. We run on virtual machines and have custom built
images that get spun up automatically if the system needs to scale (it
scales horizontally). That way I know what I have on the machines and can
upgrade to new images as needed.
I think using an automatic "apt update && apt upgrade" you will be asking
for problems. Specially if you are running one version of Python on your
own machine and another in production (running 14.04 in production is not a
good option as far as I'm concerned). You will get issues that will be
harder to find and debug.
What I really would like to run on would be things like AWS Elastic
Beanstalk - no need to configure the system at all, or in a docker image.
Regarding the AWS Beanstalk - I like the way that I don't need to provision
servers my self. And on docker you can run the same image in ALL
environments - which I think would be really useful.

Regards,

Andréas

2017-08-14 20:33 GMT+02:00 Antonis Christofides <
anto...@djangodeployment.com>:

> Hi,
>
> I generally disagree.
>
> Compiling Python on production can take some time (e.g. you may get some
> compilation parameters wrong) and makes security upgrades harder; instead
> of "apt update && apt upgrade" you'll be needing to recompile Python. It
> might not seem like a big deal, but if today you have one production
> machine, next year you will have three and the year after that you will
> have ten or more. Don't use practices that don't scale well.
>
> What I'd do would be to install Python 3.6 on my development machine and
> deploy on whatever Python version Ubuntu 14.04 has. I'd be careful to not
> use any post-3.4 features while developing (that's easy as the Python docs
> clearly have the versions marked). If an error occurs during deployment,
> chances are way higher the error will be elsewhere than in the Python
> version. Besides, upgrades are always a little risky, and if you can't
> allow the downtime, you'll need to have a staging environment as well.
>
> Of course, if there is any compelling reason to use a Python 3.6 feature,
> that's another story; but using a couple of f-strings is not compelling
> enough.
>
> Regards,
>
> Antonis
>
> Antonis Christofideshttp://djangodeployment.com
>
> On 2017-08-13 18:10, Avraham Serour wrote:
>
> I suggest using 3.6, which is the current stable release
> if your machine or the server doesn't have this version installed you may
> compile it yourself and create the virtualenv for the project from there
>
> There are some projects that help you with that, I like pythonz
> https://github.com/saghul/pythonz
>
>
> On Sun, Aug 13, 2017 at 9:33 AM, Seo Brain  wrote:
>
>> Hi, the question is about which python version suppose to use. On web
>> server is ubuntu 14.4 - python v3.4 (i assume) with virtualenv, my local is
>> python v3.5 or may be using v3.4 if i have to keep the same version on web
>> server ? v3.4 seems has issue to install on one of my windows 7, but no
>> issue on mac. or may be i suppose to use virtual-box to keep the
>> environment same everywhere dev and production server ?
>> thanks in advance. Ross
>>
>> --
>> 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 https://groups.google.com/group/django-users.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/django-users/7937063c-e3cb-44b7-b524-097b82d05d87%40googlegroups.com
>> <https://groups.google.com/d/msgid/django-users/7937063c-e3cb-44b7-b524-097b82d05d87%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> 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 https://groups.google.com/group/django-users.
> To view this discussion on the web visit https://groups.google.com/d/ms
> gid/django-users/CAFWa6tJi0OTi9sQbd23AxSuXZ12b6-YtNFp8J-q%
> 2BuP_aPhji4w%40mail.gmail.com
> <https://groups.google.com/d/msgid/django-users/CAFWa6tJi0OTi9sQbd23AxSuXZ12b6-YtNFp8J-q%2B

Re: regarding virtualenv and python version 3.5 or 3.4 or other versions

[Simon Charette]

Hello there,

I'd strongly suggest you use the same version of Python on your development 
machines and
on your servers.

You should be able to install a pre-compiled version of Python 3.5 on 
Ubuntu 14.04 LTS by
adding the deadsnakes PPA[0] running apt-get update and then apt-get 
install python3.5.

Best,
Simon

[0] https://launchpad.net/~fkrull/+archive/ubuntu/deadsnakes

Le dimanche 13 août 2017 08:51:17 UTC-4, Seo Brain a écrit :
>
> Hi, the question is about which python version suppose to use. On web 
> server is ubuntu 14.4 - python v3.4 (i assume) with virtualenv, my local is 
> python v3.5 or may be using v3.4 if i have to keep the same version on web 
> server ? v3.4 seems has issue to install on one of my windows 7, but no 
> issue on mac. or may be i suppose to use virtual-box to keep the 
> environment same everywhere dev and production server ?
> thanks in advance. Ross
>
>

-- 
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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/c1e8c6a8-48ad-40a1-b03e-229def226b6c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: regarding virtualenv and python version 3.5 or 3.4 or other versions

[Antonis Christofides]

Hi,

I generally disagree.

Compiling Python on production can take some time (e.g. you may get some
compilation parameters wrong) and makes security upgrades harder; instead of
"apt update && apt upgrade" you'll be needing to recompile Python. It might not
seem like a big deal, but if today you have one production machine, next year
you will have three and the year after that you will have ten or more. Don't use
practices that don't scale well.

What I'd do would be to install Python 3.6 on my development machine and deploy
on whatever Python version Ubuntu 14.04 has. I'd be careful to not use any
post-3.4 features while developing (that's easy as the Python docs clearly have
the versions marked). If an error occurs during deployment, chances are way
higher the error will be elsewhere than in the Python version. Besides, upgrades
are always a little risky, and if you can't allow the downtime, you'll need to
have a staging environment as well.

Of course, if there is any compelling reason to use a Python 3.6 feature, that's
another story; but using a couple of f-strings is not compelling enough.

Regards,

Antonis

Antonis Christofides
http://djangodeployment.com

On 2017-08-13 18:10, Avraham Serour wrote:
> I suggest using 3.6, which is the current stable release
> if your machine or the server doesn't have this version installed you may
> compile it yourself and create the virtualenv for the project from there
>
> There are some projects that help you with that, I like
> pythonz https://github.com/saghul/pythonz
>
>
> On Sun, Aug 13, 2017 at 9:33 AM, Seo Brain  <mailto:seob...@gmail.com>> wrote:
>
> Hi, the question is about which python version suppose to use. On web
> server is ubuntu 14.4 - python v3.4 (i assume) with virtualenv, my local
> is python v3.5 or may be using v3.4 if i have to keep the same version on
> web server ? v3.4 seems has issue to install on one of my windows 7, but
> no issue on mac. or may be i suppose to use virtual-box to keep the
> environment same everywhere dev and production server ?
> thanks in advance. Ross
>
> -- 
> 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
> <mailto:django-users+unsubscr...@googlegroups.com>.
> To post to this group, send email to django-users@googlegroups.com
> <mailto:django-users@googlegroups.com>.
> Visit this group at https://groups.google.com/group/django-users
> <https://groups.google.com/group/django-users>.
> To view this discussion on the web visit
> 
> https://groups.google.com/d/msgid/django-users/7937063c-e3cb-44b7-b524-097b82d05d87%40googlegroups.com
> 
> <https://groups.google.com/d/msgid/django-users/7937063c-e3cb-44b7-b524-097b82d05d87%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout
> <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
> <mailto:django-users+unsubscr...@googlegroups.com>.
> To post to this group, send email to django-users@googlegroups.com
> <mailto:django-users@googlegroups.com>.
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/CAFWa6tJi0OTi9sQbd23AxSuXZ12b6-YtNFp8J-q%2BuP_aPhji4w%40mail.gmail.com
> <https://groups.google.com/d/msgid/django-users/CAFWa6tJi0OTi9sQbd23AxSuXZ12b6-YtNFp8J-q%2BuP_aPhji4w%40mail.gmail.com?utm_medium=email&utm_source=footer>.
> 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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/d457e387-f9f4-716f-440a-a68426706ad2%40djangodeployment.com.
For more options, visit https://groups.google.com/d/optout.

Re: regarding virtualenv and python version 3.5 or 3.4 or other versions

[Seo Brain]

thanks for the suggestion.



On Sunday, August 13, 2017 at 8:11:57 AM UTC-7, Avraham Serour wrote:
>
> I suggest using 3.6, which is the current stable release
> if your machine or the server doesn't have this version installed you may 
> compile it yourself and create the virtualenv for the project from there
>
> There are some projects that help you with that, I like pythonz 
> https://github.com/saghul/pythonz
>
>
> On Sun, Aug 13, 2017 at 9:33 AM, Seo Brain 
> > wrote:
>
>> Hi, the question is about which python version suppose to use. On web 
>> server is ubuntu 14.4 - python v3.4 (i assume) with virtualenv, my local is 
>> python v3.5 or may be using v3.4 if i have to keep the same version on web 
>> server ? v3.4 seems has issue to install on one of my windows 7, but no 
>> issue on mac. or may be i suppose to use virtual-box to keep the 
>> environment same everywhere dev and production server ?
>> thanks in advance. Ross
>>
>> -- 
>> 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 https://groups.google.com/group/django-users.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/7937063c-e3cb-44b7-b524-097b82d05d87%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/django-users/7937063c-e3cb-44b7-b524-097b82d05d87%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> 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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/48bcfe50-effc-4688-9492-9025c9f6885d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: regarding virtualenv and python version 3.5 or 3.4 or other versions

[Avraham Serour]

I suggest using 3.6, which is the current stable release
if your machine or the server doesn't have this version installed you may
compile it yourself and create the virtualenv for the project from there

There are some projects that help you with that, I like pythonz
https://github.com/saghul/pythonz


On Sun, Aug 13, 2017 at 9:33 AM, Seo Brain  wrote:

> Hi, the question is about which python version suppose to use. On web
> server is ubuntu 14.4 - python v3.4 (i assume) with virtualenv, my local is
> python v3.5 or may be using v3.4 if i have to keep the same version on web
> server ? v3.4 seems has issue to install on one of my windows 7, but no
> issue on mac. or may be i suppose to use virtual-box to keep the
> environment same everywhere dev and production server ?
> thanks in advance. Ross
>
> --
> 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 https://groups.google.com/group/django-users.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/django-users/7937063c-e3cb-44b7-b524-097b82d05d87%40googlegroups.com
> <https://groups.google.com/d/msgid/django-users/7937063c-e3cb-44b7-b524-097b82d05d87%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> 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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAFWa6tJi0OTi9sQbd23AxSuXZ12b6-YtNFp8J-q%2BuP_aPhji4w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

regarding virtualenv and python version 3.5 or 3.4 or other versions

[Seo Brain]

Hi, the question is about which python version suppose to use. On web 
server is ubuntu 14.4 - python v3.4 (i assume) with virtualenv, my local is 
python v3.5 or may be using v3.4 if i have to keep the same version on web 
server ? v3.4 seems has issue to install on one of my windows 7, but no 
issue on mac. or may be i suppose to use virtual-box to keep the 
environment same everywhere dev and production server ?
thanks in advance. Ross

-- 
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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/7937063c-e3cb-44b7-b524-097b82d05d87%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Advice on python version for new project

[Rich Shepard]

On Tue, 16 Aug 2016, Avraham Serour wrote:


https://virtualenv.pypa.io/en/stable/


  Thanks, Avraham. Looks interesting.

Rich

Re: Advice on python version for new project

[Avraham Serour]

https://virtualenv.pypa.io/en/stable/


On Tue, Aug 16, 2016 at 1:36 AM, Rich Shepard 
wrote:

> On Tue, 16 Aug 2016, Avraham Serour wrote:
>
> you should also create a virtualenv for the project
>>
>
> Avraham,
>
>   OK. Please point me to some docs for this.
>
> Regards,
>
> Rich
>

-- 
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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAFWa6tLn6ZVhPKuAkYr8GAkvk_w2zYvj99i5ZcB06h6nBz%2BrQw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Advice on python version for new project

[Rich Shepard]

On Tue, 16 Aug 2016, Avraham Serour wrote:


you should also create a virtualenv for the project


Avraham,

  OK. Please point me to some docs for this.

Regards,

Rich

Re: Advice on python version for new project

[Avraham Serour]

you should also create a virtualenv for the project


On Tue, Aug 16, 2016 at 12:07 AM, Rich Shepard 
wrote:

> On Mon, 15 Aug 2016, Rich Shepard wrote:
>
> I'll have to learn how to get it to install in -3.5.2, too.
>>
>
>   Found the answer: pip3.
>
> Rich
>

-- 
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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAFWa6t%2BkKwuxAc4Co6OxhLqbSHEEgOZK5s%2BbCqMxGKnU9M7o-Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Advice on python version for new project

[Rich Shepard]

On Mon, 15 Aug 2016, Rich Shepard wrote:


I'll have to learn how to get it to install in -3.5.2, too.


  Found the answer: pip3.

Rich

Re: Advice on python version for new project

[Rich Shepard]

On Mon, 15 Aug 2016, Ari Davidow wrote:


If you're doing a CRM app, many advantages to using Python 3 and not having
to deal with 2's Unicode issues.


Ari,

  This is for my use only. I've outgrown the tools I've been using for my
consulting business and need to consolidate them in a single application.
Will use python3, however.

Thanks,

Rich

Re: Advice on python version for new project

[Rich Shepard]

On Mon, 15 Aug 2016, Nick Santos wrote:


I'd recommend Python 3 at this point unless you encounter a good, specific
reason to use Python 2.


Nick,

  I'll take your advice. I have both -2.7.5 and -3.5.2 installed. Using pip
to install django puts it in only the 2.7.5/site/packages/ subdirectory.
I'll have to learn how to get it to install in -3.5.2, too.

Thanks,

Rich

Re: Advice on python version for new project

[Ari Davidow]

If you're doing a CRM app, many advantages to using Python 3 and not having
to deal with 2's Unicode issues. Names do not respect a lack of Unicode,
and you want people to be able to cut and paste and/or import names as
people want to spell them.

On Mon, Aug 15, 2016 at 3:37 PM, Rich Shepard 
wrote:

>   The django web site suggests that new projects use python3 unless
> required
> dependencies are not yet available for that version. I've no idea what
> python dependencies I'll need for this job.
>
>   What I want to do is convert an abandoned php application (last upgraded
> a
> decade ago) to django. The application is XRMS, an open source CRM (client
> relationship manangement tool in my case) that is perhaps the only one that
> supposedly supported postgresql via adodb. What I learned over the weekend
> is that I cannot even install it and cannot find the reason why it's not
> connecting to the db back end.
>
>   A posting on a forum thread from 2007 reported that postgres was not
> supported unless all extensions (none of which I need) are installed, and
> all those extensions are hard coded for mysql. I have source code, schema,
> and a very full set of docs; suprizingly complete.
>
>   I suppose there's no reason to not use python-2.7.5 installed here for
> this project, unless you advise me otherwise. I also need some advice and
> guidance on how to proceed on creating a django application from the php
> source files.
>
> TIA,
>
> Rich
>
>

-- 
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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAF%2BxBDXL%2BLdu4FHd1HAh%2Bydt1DQefktosXDov%3DATfGX%3Df8rk%2Bw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Advice on python version for new project

[Nick Santos]

I'd recommend Python 3 at this point unless you encounter a good, specific
reason to use Python 2. If you use the six 
module, it's really easy to write code that can be used for both versions
without writing conditionals everywhere. If you then encounter something
that forces you to use Python 2, you can downgrade without trouble. But if
this application has anything close to the lifespan of the previous one,
you'll want to be using Python 3 if at all possible. That's without
mentioning the other benefits of Python 3 too!

-Nick 

On Mon, Aug 15, 2016 at 12:37 PM, Rich Shepard 
wrote:

>   The django web site suggests that new projects use python3 unless
> required
> dependencies are not yet available for that version. I've no idea what
> python dependencies I'll need for this job.
>
>   What I want to do is convert an abandoned php application (last upgraded
> a
> decade ago) to django. The application is XRMS, an open source CRM (client
> relationship manangement tool in my case) that is perhaps the only one that
> supposedly supported postgresql via adodb. What I learned over the weekend
> is that I cannot even install it and cannot find the reason why it's not
> connecting to the db back end.
>
>   A posting on a forum thread from 2007 reported that postgres was not
> supported unless all extensions (none of which I need) are installed, and
> all those extensions are hard coded for mysql. I have source code, schema,
> and a very full set of docs; suprizingly complete.
>
>   I suppose there's no reason to not use python-2.7.5 installed here for
> this project, unless you advise me otherwise. I also need some advice and
> guidance on how to proceed on creating a django application from the php
> source files.
>
> TIA,
>
> Rich
>
>

-- 
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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAM1S3vCsKv1XKsOnnFtgAomY2G1XnZEpMrzs%3DSdfPyXHCM9PmA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Advice on python version for new project

[Rich Shepard]

  The django web site suggests that new projects use python3 unless required
dependencies are not yet available for that version. I've no idea what
python dependencies I'll need for this job.

  What I want to do is convert an abandoned php application (last upgraded a
decade ago) to django. The application is XRMS, an open source CRM (client
relationship manangement tool in my case) that is perhaps the only one that
supposedly supported postgresql via adodb. What I learned over the weekend
is that I cannot even install it and cannot find the reason why it's not
connecting to the db back end.

  A posting on a forum thread from 2007 reported that postgres was not
supported unless all extensions (none of which I need) are installed, and
all those extensions are hard coded for mysql. I have source code, schema,
and a very full set of docs; suprizingly complete.

  I suppose there's no reason to not use python-2.7.5 installed here for
this project, unless you advise me otherwise. I also need some advice and
guidance on how to proceed on creating a django application from the php
source files.

TIA,

Rich

Re: Incorrect Python Version Being Used

[Fred Stluka]

Tom,

Excellent article!  Thanks!

--Fred

Fred Stluka -- mailto:f...@bristle.com -- http://bristle.com/~fred/
Bristle Software, Inc -- http://bristle.com -- Glad to be of service!
Open Source: Without walls and fences, we need no Windows or Gates.


On 11/15/12 12:46 PM, Tom Evans wrote:

On Thu, Nov 15, 2012 at 3:49 PM, rh  wrote:

In the djangocon lightning talk there was mention of this disconnect
between "works on runserver" but not in production env.

Not a problem restricted to django. I've been checking out a lot of
frameworks in different languages and most suffer the same malady.
i.e. everything works great locally but hauling it all into a production
env. becomes a project in itself.

It's hard to document because each env. will be different.


This is an interesting problem, which you can work around to a certain
extent. Making predictable and reproducible deployments of code is an
integral part of Software Configuration Management. SCM is a big
topic, so I'm not going to go into crazy details, but here are some
details of how we mitigate these risks at $JOB

1) Use virtualenv and pip

Virtualenv is essential. It allows you to separate the libraries you
use in your deployment from the any other python package. I recommend
using "--no-site-packages" to force virtualenv to ignore any system
site packages, but sometimes it can be necessary.

Pip is the other side of this. Pip is a simple way to specify python
packages to install. You can explicitly reference versions of
packages, or ranges of packages. Eg, "Django>1.4,<1.5" specifies that
the most recent release in the 1.4 cycle is correct. You can also have
a single file that lists all the packages required for your project to
run, usually called 'requirements.txt'. Pip will take that file, and
install all listed packages along with any dependencies.


2) Your project structure is code, and should live in source control.

Your project structure is all the files and folders that make up a
deployment, but aren't actual python code. Eg, if your deployment for
django project 'myproj' looks like this:

.
├── htdocs/
├── logs/
├── project/
│   ├── manage.py
│   └── myproj/
└── scripts/

The 'myproj' directory contains the project source code and is usually
version controlled. However, everything listed there is part of the
project deployment, and changes there must be tracked. If your project
requires a 'logs' directory, then a logs directory must be a versioned
resource that you can check out at any point in it's past.

Just as importantly, any changes that you make in the project
structure in development must be replicated to the production
deployments, and therefore must be tracked.


3) Django apps are also python libraries.

A 'django app', regardless of what it does, is also a python library.
Therefore, make sure you give it a setup.py script using distutils
that will allow you to do standard python library packaging operations
on it. Pip will happily install an app from source control, it will
even install in a manner that allows you to edit and commit changes
back to source control.
This allows you to install packages in development in the same way as
production.


4) Write a bootstrap script.

A bootstrap script is a simple shell script that does two things -
sets up a virtualenv environment, and installs a set of packages.
This combination of storing project structure in source control, using
virtualenv and pip, having a bootstrap script and having a
requirements.txt listing your required packages allows you to simply
checkout a project and run it's bootstrap script to end up with an
identical, repeatable project environment.


6) Use the capabilities of your source control to assemble a deployment

This is the tricky one where I tend to lose people! We use subversion
for source control. Subversion allows us to specify 'externals', which
are secondary subversion repositories that we want to be automatically
checked out in specific locations within another repository. You can
also have 'file externals', which is a single file (rather than an
entire repository tree) that is checked out at a specific location.

The benefit of this is that you can use your project structure
repository as a basis for a deployment on a single site, by
duplicating it for each server that you wish to deploy on.
On each one, you would have an external adding the project source code
in the right place. You would have a file external that pulls in a
'requirements.txt' file correct for this project into the right place.
You would have another file external that pulls in the correct
settings.py (or settings_local.py if that is what you prefer).


7) Use South

Use south for database migrations. If you aren't doing this already,
you should be! Schemas rarely stay static, you need good ways of
managing that change.


8) Use Fabric

Re: Incorrect Python Version Being Used

[Tom Evans]

On Thu, Nov 15, 2012 at 3:49 PM, rh  wrote:
> In the djangocon lightning talk there was mention of this disconnect
> between "works on runserver" but not in production env.
>
> Not a problem restricted to django. I've been checking out a lot of
> frameworks in different languages and most suffer the same malady.
> i.e. everything works great locally but hauling it all into a production
> env. becomes a project in itself.
>
> It's hard to document because each env. will be different.
>

This is an interesting problem, which you can work around to a certain
extent. Making predictable and reproducible deployments of code is an
integral part of Software Configuration Management. SCM is a big
topic, so I'm not going to go into crazy details, but here are some
details of how we mitigate these risks at $JOB

1) Use virtualenv and pip

Virtualenv is essential. It allows you to separate the libraries you
use in your deployment from the any other python package. I recommend
using "--no-site-packages" to force virtualenv to ignore any system
site packages, but sometimes it can be necessary.

Pip is the other side of this. Pip is a simple way to specify python
packages to install. You can explicitly reference versions of
packages, or ranges of packages. Eg, "Django>1.4,<1.5" specifies that
the most recent release in the 1.4 cycle is correct. You can also have
a single file that lists all the packages required for your project to
run, usually called 'requirements.txt'. Pip will take that file, and
install all listed packages along with any dependencies.


2) Your project structure is code, and should live in source control.

Your project structure is all the files and folders that make up a
deployment, but aren't actual python code. Eg, if your deployment for
django project 'myproj' looks like this:

.
├── htdocs/
├── logs/
├── project/
│   ├── manage.py
│   └── myproj/
└── scripts/

The 'myproj' directory contains the project source code and is usually
version controlled. However, everything listed there is part of the
project deployment, and changes there must be tracked. If your project
requires a 'logs' directory, then a logs directory must be a versioned
resource that you can check out at any point in it's past.

Just as importantly, any changes that you make in the project
structure in development must be replicated to the production
deployments, and therefore must be tracked.


3) Django apps are also python libraries.

A 'django app', regardless of what it does, is also a python library.
Therefore, make sure you give it a setup.py script using distutils
that will allow you to do standard python library packaging operations
on it. Pip will happily install an app from source control, it will
even install in a manner that allows you to edit and commit changes
back to source control.
This allows you to install packages in development in the same way as
production.


4) Write a bootstrap script.

A bootstrap script is a simple shell script that does two things -
sets up a virtualenv environment, and installs a set of packages.
This combination of storing project structure in source control, using
virtualenv and pip, having a bootstrap script and having a
requirements.txt listing your required packages allows you to simply
checkout a project and run it's bootstrap script to end up with an
identical, repeatable project environment.


6) Use the capabilities of your source control to assemble a deployment

This is the tricky one where I tend to lose people! We use subversion
for source control. Subversion allows us to specify 'externals', which
are secondary subversion repositories that we want to be automatically
checked out in specific locations within another repository. You can
also have 'file externals', which is a single file (rather than an
entire repository tree) that is checked out at a specific location.

The benefit of this is that you can use your project structure
repository as a basis for a deployment on a single site, by
duplicating it for each server that you wish to deploy on.
On each one, you would have an external adding the project source code
in the right place. You would have a file external that pulls in a
'requirements.txt' file correct for this project into the right place.
You would have another file external that pulls in the correct
settings.py (or settings_local.py if that is what you prefer).


7) Use South

Use south for database migrations. If you aren't doing this already,
you should be! Schemas rarely stay static, you need good ways of
managing that change.


8) Use Fabric

Fabric is a clever system for writing scripts to do things on remote
servers. Work out the steps required to update your project source
code, libraries, deploy migrations, and codify it into a fabric
fabfile. Never make a mistake in deployment again!


There is more to it than this of course (there is a lot more to each
of these steps even!), but these simple ideas allowed us reliable and
predictable deployments and

Re: Incorrect Python Version Being Used

[Bestrafung]

Thanks for the info. I built mine using:
./configure --with-apxs=/usr/local/apache/bin/apxs 
--with-python=/opt/python2.7/bin/python

I'm fairly certain everything is good there. I'm able to load both projects 
individually using "python manage.py runserver 0.0.0.0:8000" without issue. 
The trouble now comes from trying to access them via the Apache server. 
There's some kind of problem with the bootstrap .wsgi file(s) and I also 
need to figure out how to load both at the same time as Apache spits an 
error and refuses to build the vhost with multiple projects. I hope some of 
this helps others but my issue is definitely in the mod_wsgi/Apache setup 
now.


On Tuesday, November 6, 2012 1:45:49 PM UTC-5, Nikolas Stevenson-Molnar 
wrote:
>
>  If you're running via mod_wsgi, then you need to look at which version of 
> Python mod_wsgi was built with. Probably *not *2.7 in that case.
>
>
> http://code.google.com/p/modwsgi/wiki/InstallationIssues#Multiple_Python_Versions
>
> _Nik
>  

-- 
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/-/prxw6dH87zsJ.
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: Incorrect Python Version Being Used

[Nikolas Stevenson-Molnar]

If you're running via mod_wsgi, then you need to look at which version
of Python mod_wsgi was built with. Probably /not /2.7 in that case.

http://code.google.com/p/modwsgi/wiki/InstallationIssues#Multiple_Python_Versions

_Nik

On 11/6/2012 10:02 AM, Bestrafung wrote:
> Thank you for the info. That's how I've been doing it but assumed
> something wasn't right as it wasn't working and I keep getting errors.
> I think I've ruled out python as the problem Need to start looking at
> the mod_wsgi and Apache setup.
>
> I have another post regarding Apache errors I will get back to, is
> there a way to close this topic?
>
> On Tuesday, November 6, 2012 11:14:53 AM UTC-5, Nikolas
> Stevenson-Molnar wrote:
>
> Whenever you run a Django command (e.g., startapp, runserver),
> just use
> the full path to your Python 2.7 interpreter. For example:
>
> $ /opt/python2.7/bin/python manage.py runserver 80
>
> Similarly, if you're installing packages via pip or easy_install:
>
> $ /opt/python2.7/bin/pip install some_package
> $ /opt/python2.7/bin/easy_install some_package
>
> _Nik
>
> On 11/6/2012 7:09 AM, Bestrafung wrote:
> > I have been running into this problem for a long while trying to
> setup
> > my first Django project and I keep coming back to this problem.
> I am
> > relatively new when it come to Linux, I'm learning but still have a
> > long way to go. I am using CentOS 5.8 cPanel which comes with
> Python
> > 2.4. Following instructions I found online for setting up Django
> with
> > cPanel I compiled/installed Python 2.7 from source to
> /opt/python2.7
> > and set an alias (alias python="/opt/python2.7/bin/python") in the
> > root and user's .bash_profile and python 2.7 launches as
> expected when
> > you use the python command. Every time I try to start a project or
> > work with it however the system default python 2.4 keeps popping
> up. I
> > think this may be the single cause of all of my issues. When
> starting
> > a project I have just appended the python command to make sure it
> > started with the correct version. I believe that once the
> project is
> > started it isn't working because everything is still trying to use
> > 2.4. Is there a way to make Django use my 2.7 install instead of
> 2.4
> > without breaking the system by making the 2.7 system default?
> > --
> > 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/-/WqpZIEJqalcJ
> .
> > To post to this group, send email to django...@googlegroups.com
> .
> > To unsubscribe from this group, send email to
> > django-users...@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 view this discussion on the web visit
> https://groups.google.com/d/msg/django-users/-/OVUWdCah_fwJ.
> 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.

Re: Incorrect Python Version Being Used

[Bestrafung]

I'm not familiar with how to do this but the suggestion is noted. I will 
look into it. Thanks.

On Tuesday, November 6, 2012 11:26:41 AM UTC-5, Thomas wrote:
>
> Use virtualenv. Always. 
>
>  - Tom 
> > -- 
> > 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/-/WqpZIEJqalcJ. 
> > To post to this group, send email to 
> > django...@googlegroups.com. 
>
> > To unsubscribe from this group, send email to 
> > django-users...@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 view this discussion on the web visit 
https://groups.google.com/d/msg/django-users/-/yd9js8Dy6L0J.
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: Incorrect Python Version Being Used

[Bestrafung]

Thank you for the info. That's how I've been doing it but assumed something 
wasn't right as it wasn't working and I keep getting errors. I think I've 
ruled out python as the problem Need to start looking at the mod_wsgi and 
Apache setup.

I have another post regarding Apache errors I will get back to, is there a 
way to close this topic?

On Tuesday, November 6, 2012 11:14:53 AM UTC-5, Nikolas Stevenson-Molnar 
wrote:
>
> Whenever you run a Django command (e.g., startapp, runserver), just use 
> the full path to your Python 2.7 interpreter. For example: 
>
> $ /opt/python2.7/bin/python manage.py runserver 80 
>
> Similarly, if you're installing packages via pip or easy_install: 
>
> $ /opt/python2.7/bin/pip install some_package 
> $ /opt/python2.7/bin/easy_install some_package 
>
> _Nik 
>
> On 11/6/2012 7:09 AM, Bestrafung wrote: 
> > I have been running into this problem for a long while trying to setup 
> > my first Django project and I keep coming back to this problem. I am 
> > relatively new when it come to Linux, I'm learning but still have a 
> > long way to go. I am using CentOS 5.8 cPanel which comes with Python 
> > 2.4. Following instructions I found online for setting up Django with 
> > cPanel I compiled/installed Python 2.7 from source to /opt/python2.7 
> > and set an alias (alias python="/opt/python2.7/bin/python") in the 
> > root and user's .bash_profile and python 2.7 launches as expected when 
> > you use the python command. Every time I try to start a project or 
> > work with it however the system default python 2.4 keeps popping up. I 
> > think this may be the single cause of all of my issues. When starting 
> > a project I have just appended the python command to make sure it 
> > started with the correct version. I believe that once the project is 
> > started it isn't working because everything is still trying to use 
> > 2.4. Is there a way to make Django use my 2.7 install instead of 2.4 
> > without breaking the system by making the 2.7 system default? 
> > -- 
> > 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/-/WqpZIEJqalcJ. 
> > To post to this group, send email to 
> > django...@googlegroups.com. 
>
> > To unsubscribe from this group, send email to 
> > django-users...@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 view this discussion on the web visit 
https://groups.google.com/d/msg/django-users/-/OVUWdCah_fwJ.
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: Incorrect Python Version Being Used

[Thomas Lockhart]

On 11/6/12 7:09 AM, Bestrafung wrote:
I have been running into this problem for a long while trying to setup 
my first Django project and I keep coming back to this problem. I am 
relatively new when it come to Linux, I'm learning but still have a 
long way to go. I am using CentOS 5.8 cPanel which comes with Python 
2.4. Following instructions I found online for setting up Django with 
cPanel I compiled/installed Python 2.7 from source to /opt/python2.7 
and set an alias (alias python="/opt/python2.7/bin/python") in the 
root and user's .bash_profile and python 2.7 launches as expected when 
you use the python command. Every time I try to start a project or 
work with it however the system default python 2.4 keeps popping up. I 
think this may be the single cause of all of my issues. When starting 
a project I have just appended the python command to make sure it 
started with the correct version. I believe that once the project is 
started it isn't working because everything is still trying to use 
2.4. Is there a way to make Django use my 2.7 install instead of 2.4 
without breaking the system by making the 2.7 system default?

Use virtualenv. Always.

- Tom

--
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/-/WqpZIEJqalcJ.

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.

Re: Incorrect Python Version Being Used

[Nikolas Stevenson-Molnar]

Whenever you run a Django command (e.g., startapp, runserver), just use
the full path to your Python 2.7 interpreter. For example:

$ /opt/python2.7/bin/python manage.py runserver 80

Similarly, if you're installing packages via pip or easy_install:

$ /opt/python2.7/bin/pip install some_package
$ /opt/python2.7/bin/easy_install some_package

_Nik

On 11/6/2012 7:09 AM, Bestrafung wrote:
> I have been running into this problem for a long while trying to setup
> my first Django project and I keep coming back to this problem. I am
> relatively new when it come to Linux, I'm learning but still have a
> long way to go. I am using CentOS 5.8 cPanel which comes with Python
> 2.4. Following instructions I found online for setting up Django with
> cPanel I compiled/installed Python 2.7 from source to /opt/python2.7
> and set an alias (alias python="/opt/python2.7/bin/python") in the
> root and user's .bash_profile and python 2.7 launches as expected when
> you use the python command. Every time I try to start a project or
> work with it however the system default python 2.4 keeps popping up. I
> think this may be the single cause of all of my issues. When starting
> a project I have just appended the python command to make sure it
> started with the correct version. I believe that once the project is
> started it isn't working because everything is still trying to use
> 2.4. Is there a way to make Django use my 2.7 install instead of 2.4
> without breaking the system by making the 2.7 system default?
> -- 
> 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/-/WqpZIEJqalcJ.
> 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.

Incorrect Python Version Being Used

[Bestrafung]

I have been running into this problem for a long while trying to setup my 
first Django project and I keep coming back to this problem. I am 
relatively new when it come to Linux, I'm learning but still have a long 
way to go. I am using CentOS 5.8 cPanel which comes with Python 2.4. 
Following instructions I found online for setting up Django with cPanel I 
compiled/installed Python 2.7 from source to /opt/python2.7 and set an 
alias (alias python="/opt/python2.7/bin/python") in the root and user's 
.bash_profile and python 2.7 launches as expected when you use the python 
command. Every time I try to start a project or work with it however the 
system default python 2.4 keeps popping up. I think this may be the single 
cause of all of my issues. When starting a project I have just appended the 
python command to make sure it started with the correct version. I believe 
that once the project is started it isn't working because everything is 
still trying to use 2.4. Is there a way to make Django use my 2.7 install 
instead of 2.4 without breaking the system by making the 2.7 system default?

-- 
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/-/WqpZIEJqalcJ.
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: Django/Python version compatibility

[Simone Federici]

On Mon, Mar 19, 2012 at 21:52, Chiproller  wrote:

> So will 1.4 be compatible with Python 3.X?  I am wondering how best to
> learn Python for Django if I'm learning from Python books that cover
> (like most new books) 3.X.  Any suggestions?
>

Django 1.4 => [ Python2.5, Python2.6, Python2.7 ]
Django 1.5 maybe=>  [Python2.5+,  Python3.3]

Actually python2.7 is the best solution to begin, if you like the syntax of
python 3x you can use import __future__

-- 
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: Django/Python version compatibility

[Chiproller]

So will 1.4 be compatible with Python 3.X?  I am wondering how best to
learn Python for Django if I'm learning from Python books that cover
(like most new books) 3.X.  Any suggestions?

On Mar 19, 12:50 pm, Joel Goldstick  wrote:
> On Mon, Mar 19, 2012 at 11:41 AM, Shawn Milochik  wrote:
> > Django won't support 3.x for a while. You can't go wrong with 2.7 for now.
>
> >https://www.djangoproject.com/weblog/2012/mar/13/py3k/
>
> > Shawn
>
> > --
> > 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.
>
> So your other choice is whether to go with django 1.3 or the new 1.4
> being released some time in the coming days.  Probably best to go with
> 1.4 since they keep making it better, but there are differences
> between the new version and the old version's way of setting up
> directories, so beware that third party tutorials will have to be
> tweeked with to get going in 1.4
>
> --
> Joel Goldstick

-- 
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: Django/Python version compatibility

[Joel Goldstick]

On Mon, Mar 19, 2012 at 11:41 AM, Shawn Milochik  wrote:
> Django won't support 3.x for a while. You can't go wrong with 2.7 for now.
>
> https://www.djangoproject.com/weblog/2012/mar/13/py3k/
>
> Shawn
>
>
> --
> 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.
>

So your other choice is whether to go with django 1.3 or the new 1.4
being released some time in the coming days.  Probably best to go with
1.4 since they keep making it better, but there are differences
between the new version and the old version's way of setting up
directories, so beware that third party tutorials will have to be
tweeked with to get going in 1.4

-- 
Joel Goldstick

-- 
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: Django/Python version compatibility

[Shawn Milochik]

Django won't support 3.x for a while. You can't go wrong with 2.7 for now.

https://www.djangoproject.com/weblog/2012/mar/13/py3k/

Shawn

--
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.

Django/Python version compatibility

[Chiproller]

I am just learning Python and plan to use it for web development so I
will be using Django.  Python version 2.7 was pre-installed on my
macbook and I'm wondering if I installed the latest 3.* version would
Django not work at all when I get to the point of learning Django?

Reason I ask, is that I'm using a number of resources to learn Python
(Learning Python, Programming Python, Learn Python the Hard Way) and
some of these books use 3.0 code.

Jim

-- 
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: python version

[alexarsh]

Thanks for the fast reply.
And how can I find all python versions installed on a machine?

On Apr 5, 7:21 pm, Alex Gaynor  wrote:
> On Sun, Apr 5, 2009 at 12:16 PM, knight  wrote:
>
> > Hi,
>
> > I have 2 servers with my django app:
> > The first one has python2.5 as default python and the second don't (It
> > has python2.5 installed together with the older version).
> > I want to run dumpdata from my application and I have the following
> > problem:
> > If I call: "python manage.py dumpdata" the second server won't work.
> > If I call: "python2.5 manage.py dumpdata" the first server won't
> > work.
> > I mean, I will get the following error:
>
> > Traceback (most recent call last):
> >  File "manage.py", line 2, in 
> >    from django.core.management import execute_manager
> > ImportError: No module named django.core.management
>
> > How can I find the right python version to call? Maybe I can take it
> > from PYTHONPATH? If yes, where can I find it?
>
> > Thanks, Alex A.
>
> Getting errors like that means you have Django installed to the
> site-packages dir of that python version, to figure out which python version
> to run all you should need to do is go to each python interpretter and do
> import django, and whichever one doesn't give an error is the right one to
> use.
>
> Alex
>
> --
> "I disapprove of what you say, but I will defend to the death your right to
> say it." --Voltaire
> "The people's good is the highest law."--Cicero
--~--~-~--~~~---~--~~
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: python version

[Alex Gaynor]

On Sun, Apr 5, 2009 at 12:16 PM, knight  wrote:

>
> Hi,
>
> I have 2 servers with my django app:
> The first one has python2.5 as default python and the second don't (It
> has python2.5 installed together with the older version).
> I want to run dumpdata from my application and I have the following
> problem:
> If I call: "python manage.py dumpdata" the second server won't work.
> If I call: "python2.5 manage.py dumpdata" the first server won't
> work.
> I mean, I will get the following error:
>
> Traceback (most recent call last):
>  File "manage.py", line 2, in 
>from django.core.management import execute_manager
> ImportError: No module named django.core.management
>
> How can I find the right python version to call? Maybe I can take it
> from PYTHONPATH? If yes, where can I find it?
>
> Thanks, Alex A.
>
> >
>
Getting errors like that means you have Django installed to the
site-packages dir of that python version, to figure out which python version
to run all you should need to do is go to each python interpretter and do
import django, and whichever one doesn't give an error is the right one to
use.

Alex

-- 
"I disapprove of what you say, but I will defend to the death your right to
say it." --Voltaire
"The people's good is the highest law."--Cicero

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

python version

[knight]

Hi,

I have 2 servers with my django app:
The first one has python2.5 as default python and the second don't (It
has python2.5 installed together with the older version).
I want to run dumpdata from my application and I have the following
problem:
If I call: "python manage.py dumpdata" the second server won't work.
If I call: "python2.5 manage.py dumpdata" the first server won't
work.
I mean, I will get the following error:

Traceback (most recent call last):
  File "manage.py", line 2, in 
from django.core.management import execute_manager
ImportError: No module named django.core.management

How can I find the right python version to call? Maybe I can take it
from PYTHONPATH? If yes, where can I find it?

Thanks, Alex A.

--~--~-~--~~~---~--~~
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: How to change python version in ubuntu???

[Steve Holden]

DragonSlayre wrote:
>
> On Jan 27, 4:11 pm, Steve Holden  wrote:
>   
>> DragonSlayre wrote:
>>
>> 
>>> On Jan 27, 3:15 pm, Steve Holden  wrote:
>>>   
 DragonSlayre wrote:
 
>>> How do you do this?
>>>   
>> http://www.swc.scipy.org/lec/shell02.html
>>
>> regards
>>  Steve
>> 
>
> WOW, that explains it all...  Looks about as good as every other thing
> that I've read on the net.
> Ok, so I do a set | less - hey there's no Environment variable
> with PYTHON in it. - who cares though right - now I know how to use
> grep... yay!!
>
> This is what F**ks me off with most of the developers out there - so
> vague in documentation (if it exists).
>
> I know you are probably just trying to help Steve, but if you know how
> to do this, is it so hard just to say how?  It's very frustrating to
> spend hours and hours trying to find out how to do something so
> simple, and still have no answer.  Personally - I wish there was a
> radio button that I could select to switch between python versions,
> but unfortunately, a radio button just isn't as superior as a
> terminal.
>
> The link provided looks like a great reference, but unfortunately it's
> like giving someone a toolkit and expecting them to build a house from
> it.
>   
I'm sorry if you found that reference confusing. This indicates that you
may need to climb the computing curve a little further before you can
expect to get the most from Django. It is after all primarily a
programmer's framework.

[sigh] In essence, the PATH shell environment variable in most
Linux/UNIX shells today is a colon-separated list of directories. When
you issue a command the shell performs various substitutions (filename,
shell variable, history, alias, and so on) and ends up with a list of
tokens. Usually the tokens are separated by spaces, though you can
change this behavior by setting specific environment variables.

If the first token contains any slashes it's interpreted as the path to
the program to be executed (relative to the current direct directory,
unless it starts with a slash in which case it's an absolute path).
Otherwise the shell looks for a file of that name in each of the
directories on the PATH until it either finds it or exhausts the PATH.

So let's say you have python 2.5 installed as /usr/bin/python and 2.6
installed as /usr/local/bin/python. When you type "python ..." at the
command line, which of those is executed depends on the order of the
directories in the PATH.

There's more, but that's the scoop. Hope this helps.

regards
 Steve


--~--~-~--~~~---~--~~
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: How to change python version in ubuntu???

[shaleh]

On Tue Jan 27 12:12 , DragonSlayre  sent:

>
>Thanks Waylan  -
http://achinghead.com/archive/83/installing-multiple-versions-python/
>is just what I needed.
>
>Thanks Shaleh,
>
>I appreciate the detailed explanation :)
>Yes - the shell is something that I have to get more familiar with -
>I've only really recently started using ubuntu for development so am
>on a bit of a learning journey.
>

We learn something new everyday. When we stop learning we stop growing. Stop
growing and you are as good as dead (-: The book I linked to should really help
you on this journey. GUIs are very useful but sometimes getting your hands dirty
on the command line is a good thing. (-:

>So it seems pretty easy to invoke the version of python I want to use,
>and using symbolic links make sense (especially after seeing Waylan's
>link).
>
>Just a couple of questions:
>
>I didn't quite get what you were referring to with the Django command
>line tool, and Django scripts - are you talking about django-
>admin.py ?

yes, that is what I meant.

>When you install a python package from the package manager or using
>apt-get, is there some way to tell it to install into a specific
>version of python, or does it use the python symlink /usr/bin/python,
>or something else? - Waylan installed easy_install for each python
>version in his example (so he could install packages for different
>python versions).
>

Typically, if a python library package is tied to a specific python version the
version will be in the package name. For instance idle-python2.4 and
idle-python2.5. Otherwise, the package will install into a generic python
accessible location and be available to all version of python installed. Look at
/usr/lib and /usr/share. You should see multiple directories with the word
'python' in their name. Digging through their contents should make things more 
clear.

I have never played with easy_install, so I can not comment on how that would
interact with prebuilt Ubuntu packages. I usually use Debian's unstable version
aka Sid. unstable in this case is the scientific definition meaning often
changing and not the more common usage of might break at any moment (-:

One more helpful tip. Go to the python.org website. There is a mailing list 
there
called 'python tutor'. It is meant for all kinds of Python newbie questions --
ask about code, ask about packages, whatever. The people on the list have been
there for quite a few years and will be very careful to explain things (-: Just
the archives from that list may be helpful to you, depending on how you learn 
new
things.


--~--~-~--~~~---~--~~
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: How to change python version in ubuntu???

[DragonSlayre]

Thanks Waylan  - 
http://achinghead.com/archive/83/installing-multiple-versions-python/
is just what I needed.

Thanks Shaleh,

I appreciate the detailed explanation :)
Yes - the shell is something that I have to get more familiar with -
I've only really recently started using ubuntu for development so am
on a bit of a learning journey.

So it seems pretty easy to invoke the version of python I want to use,
and using symbolic links make sense (especially after seeing Waylan's
link).

Just a couple of questions:

I didn't quite get what you were referring to with the Django command
line tool, and Django scripts - are you talking about django-
admin.py ?
When you install a python package from the package manager or using
apt-get, is there some way to tell it to install into a specific
version of python, or does it use the python symlink /usr/bin/python,
or something else? - Waylan installed easy_install for each python
version in his example (so he could install packages for different
python versions).


Thanks a lot,

Things are becoming much clearer now.


--~--~-~--~~~---~--~~
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: How to change python version in ubuntu???

[shaleh]

>
>On Mon Jan 26 17:51 , DragonSlayre  sent:
>
>>
>>
>>
>>On Jan 27, 1:41 pm, sha...@speakeasy.net> wrote:
>>
>>> Does this help? Found via google and ubuntu
>forums.https://launchpad.net/~doko/+archive
>>>
>>> Sorry, I run Debian (which ubuntu is based on), I just apt-get install all 
>>> of the
>>> available python versions and then run /usr/bin/python to test things.
>>
>>The problem isn't installing python, which can be done through the
>>package manager or with apt-get, but the problem is for example
>>changing back to 2.5 once 2.6 is installed.
>
>It should install a binary as python2.6. It should not touch your python2.5
>binary. Then you simply call the version you are interested in. Or change the
>/usr/bin/python symlink.
>

I just say your mail to Steve asking for people to be very clear in their
explanations. Sorry, many of us make the (incorrect) assumption that if you are
using Linux, experimenting with the package managers, etc. that there is a
certain level of shell competency. This is in no way intended as a jab at you or
others. When many of us started doing this, we were thrown into the deep water
and struggled to swim. These days with all of the GUI support, easy OS installs,
etc. it is easy for us to forget that today's newbie did not have to fight as
hard as those in the past. Again, this is not a "you have not bled enough, leave
us alone" comment. Just explaining where many of us are coming from.

May I recommend a great book called Unix Shells by Example.
http://www.amazon.com/UNIX-R-Shells-Example-4th/dp/013147572X/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1233081731&sr=8-1
(note there is no referral ID in that link). The lady who wrote it does a great
job. It explains all of the common shell tools. Read it, pass it around to your
friends. I leave a copy at work to hand over to new hires.

Now back to the topic at hand.

In Debian and ubuntu, great care is taken to support upgrading and testing. Each
Python version will be installed in a version specific directory. So python 2.4
will be /usr/bin/python2.4 and have its files stored in /usr/lib/python2.4/...,
etc. This means you can install as many python packages as you like and then 
just
invoke the correct binary for the task at hand. What this means for you is 
python
2.6 packages should be safe to install and can be invoked as python2.6. You can
edit the Django command line tool to call python2.6 instead of just python. Then
the right version will be called.

When the distribution considers a version of python the standard for a release
all they do is set the /usr/bin/python symbolic link to the correct binary. It 
is
a bad idea to change this link unless you are sure all of the software you need
can run safely with that python version.

$PYTHONHOME is not necessarily the variable you need to set. Sometimes it is, it
all depends on how you installed Python. If you only use packages, then simply
invoking the correct binary is 100% the easiest way and requires no other
changes. If you compile from sources, then be sure to place the output in
/usr/local or /opt/. When you then call /usr/local/bin/python or
/opt/python2.6/bin/python the right files should be used. But all of this 
assumes
you update the Django scripts to call the right python and not just depend on
/usr/bin/python or '/usr/bin/env python' to find the right one. It is OK to edit
this scripts, honest. (-:


--~--~-~--~~~---~--~~
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: How to change python version in ubuntu???

[shaleh]

On Mon Jan 26 17:51 , DragonSlayre  sent:

>
>
>
>On Jan 27, 1:41 pm, sha...@speakeasy.net> wrote:
>
>> Does this help? Found via google and ubuntu
forums.https://launchpad.net/~doko/+archive
>>
>> Sorry, I run Debian (which ubuntu is based on), I just apt-get install all 
>> of the
>> available python versions and then run /usr/bin/python to test things.
>
>The problem isn't installing python, which can be done through the
>package manager or with apt-get, but the problem is for example
>changing back to 2.5 once 2.6 is installed.

It should install a binary as python2.6. It should not touch your python2.5
binary. Then you simply call the version you are interested in. Or change the
/usr/bin/python symlink.

--~--~-~--~~~---~--~~
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: How to change python version in ubuntu???

[waylan]

On Jan 26, 7:28 pm, DragonSlayre  wrote:
> Ok, well I reinstalled ubuntu.
>
> It'd still be good to know how to change python versions easily, if
> anybody knows how to do this - it seems like it's not documented
> anywhere :(

A little while back I wrote up how I installed all versions from 2.3
up through 3.0 on my system[1]. To switch between them, I just use
python on the command line. So if I want 2.4 I type
``python2.4`` etc. One thing I didn't mention is that the ``python``
command (without a version) is just a symbolic link to the default
(``python2.5`` in my case). To change that, I can just replace that
link with one that points to whatever version I want as the default.

[1]: http://achinghead.com/archive/83/installing-multiple-versions-python/
--~--~-~--~~~---~--~~
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: How to change python version in ubuntu???

[DragonSlayre]

On Jan 27, 4:11 pm, Steve Holden  wrote:
> DragonSlayre wrote:
>
> > On Jan 27, 3:15 pm, Steve Holden  wrote:
>
> >> DragonSlayre wrote:
> > How do you do this?
>
> http://www.swc.scipy.org/lec/shell02.html
>
> regards
>  Steve

WOW, that explains it all...  Looks about as good as every other thing
that I've read on the net.
Ok, so I do a set | less - hey there's no Environment variable
with PYTHON in it. - who cares though right - now I know how to use
grep... yay!!

This is what F**ks me off with most of the developers out there - so
vague in documentation (if it exists).

I know you are probably just trying to help Steve, but if you know how
to do this, is it so hard just to say how?  It's very frustrating to
spend hours and hours trying to find out how to do something so
simple, and still have no answer.  Personally - I wish there was a
radio button that I could select to switch between python versions,
but unfortunately, a radio button just isn't as superior as a
terminal.

The link provided looks like a great reference, but unfortunately it's
like giving someone a toolkit and expecting them to build a house from
it.
--~--~-~--~~~---~--~~
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: How to change python version in ubuntu???

[Steve Holden]

DragonSlayre wrote:
>
> On Jan 27, 3:15 pm, Steve Holden  wrote:
>   
>> DragonSlayre wrote:
>> That's most easily done by controlling your PATH so the the version you
>> want to prefer is found first when python is called for.
>>
>> regards
>>  Steve
>> 
>
> How do you do this?
>   
http://www.swc.scipy.org/lec/shell02.html

regards
 Steve


--~--~-~--~~~---~--~~
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: How to change python version in ubuntu???

[DragonSlayre]

RE Steve - I tried earlier to change the PYTHONHOME variable (seen in
the man pages - http://linux.die.net/man/1/python), the python path
urls changed, but they were a bit screwed up.

The way I changed it was by editing the .bashrc (hidden) file in my
home directory.  I think I wrote something like export PYTHONHOME=/usr/
lib/python2.5

I'm just hacking around as I couldn't find anything explicit enough to
say how to change the python version.
--~--~-~--~~~---~--~~
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: How to change python version in ubuntu???

[DragonSlayre]

On Jan 27, 3:15 pm, Steve Holden  wrote:
> DragonSlayre wrote:
> That's most easily done by controlling your PATH so the the version you
> want to prefer is found first when python is called for.
>
> regards
>  Steve

How do you do this?
--~--~-~--~~~---~--~~
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: How to change python version in ubuntu???

[Steve Holden]

DragonSlayre wrote:
>
> On Jan 27, 1:41 pm,  wrote:
>
>   
>> Does this help? Found via google and ubuntu 
>> forums.https://launchpad.net/~doko/+archive
>>
>> Sorry, I run Debian (which ubuntu is based on), I just apt-get install all 
>> of the
>> available python versions and then run /usr/bin/python to test 
>> things.
>> 
>
> The problem isn't installing python, which can be done through the
> package manager or with apt-get, but the problem is for example
> changing back to 2.5 once 2.6 is installed.
>   
That's most easily done by controlling your PATH so the the version you
want to prefer is found first when python is called for.

regards
 Steve


--~--~-~--~~~---~--~~
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: How to change python version in ubuntu???

[DragonSlayre]

On Jan 27, 1:41 pm,  wrote:

> Does this help? Found via google and ubuntu 
> forums.https://launchpad.net/~doko/+archive
>
> Sorry, I run Debian (which ubuntu is based on), I just apt-get install all of 
> the
> available python versions and then run /usr/bin/python to test 
> things.

The problem isn't installing python, which can be done through the
package manager or with apt-get, but the problem is for example
changing back to 2.5 once 2.6 is installed.
--~--~-~--~~~---~--~~
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: How to change python version in ubuntu???

[shaleh]

On Mon Jan 26 16:28 , DragonSlayre  sent:

>
>Ok, well I reinstalled ubuntu.
>
>It'd still be good to know how to change python versions easily, if
>anybody knows how to do this - it seems like it's not documented
>anywhere :(

Does this help? Found via google and ubuntu forums.
https://launchpad.net/~doko/+archive

Sorry, I run Debian (which ubuntu is based on), I just apt-get install all of 
the
available python versions and then run /usr/bin/python to test things.


--~--~-~--~~~---~--~~
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: How to change python version in ubuntu???

[DragonSlayre]

Ok, well I reinstalled ubuntu.

It'd still be good to know how to change python versions easily, if
anybody knows how to do this - it seems like it's not documented
anywhere :(
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

How to change python version in ubuntu???

[DragonSlayre]

Hi,

I've made a total mess of python (I installed python2.6 from source,
installed python 2.6 from an installer (http://jaredforsyth.com/
content/install-python-26-ubuntu)).  The source version installed
into /usr/local/, and the installer version installed into /usr/.

After installing python from source, I installed Django (which
installed into the correct location).  I then tried installing PIL
(python imaging library) - which didn't install into the correct
location.  That's why I thought I'd give the installer a go.

I then decided that I should try revert back to python 2.5.  So I
deleted the python2.6 files and folders from /usr/local/lib, /usr/
local/bin, /usr/lib/, /usr/bin/.

when I run python though, it still says it's python 2.6.1..

I thought that trying to reinstall python2.5 again might overwrite the
python version, but unfortunately it doesn't.

I looked up the python doc in the man pages (http://
manpages.ubuntu.com/manpages/intrepid/en/man1/python.1.html), and
searched over the internet, but haven't found out how to revert to a
previous version of python, or change the version.

The only real viable solution for me at the moment is to reinstall
ubuntu and start again - although I would consider this to be a bit of
a cheats way - as in the end, I haven't really learnt anything (apart
from the fact that I probably don't want to mess with the python
versions!)


Surely somebody must know how to setup which python version they wish
to use?



Thanks for your help,


Louis

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

mod_python Python version and executable don't match

[Alex Robbins]

I am attempting to deploy django on a RHEL 5 server. My team decided
they would really like Python 2.5, instead of the 2.4 that Red Hat
supports and ships with. I installed python 2.5 to /usr/local so as
not to interfere with the system's python living at /usr/lib. Then I
downloaded the mod_python source and compiled against the new python
installation. Then I did the traditional ./configure; make; make
install (with all of the --with-python=... --with-apxs=...). At this
point I have mod_python running, and the error pages report Python
version 2.5.2. Unfortunately, the Python Executable reports itself as /
usr/bin/python. That executable is version 2.4.3. I guess my question
is, how can the version and the executable not match?
I appended some interactive sessions to (hopefully) show I am not
insane. Thanks in advance.

>From Error Page:
Python Executable:  /usr/bin/python
Python Version: 2.5.2

[EMAIL PROTECTED] ~]$ /usr/bin/python
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 sys
>>> print sys.version
2.4.3 (#1, Mar 14 2007, 18:51:08)
[GCC 4.1.1 20070105 (Red Hat 4.1.1-52)]
>>> print sys.executable
/usr/bin/python
>>>
[EMAIL PROTECTED] ~]$ python2.5
Python 2.5.2 (r252:60911, Apr 19 2008, 06:33:52)
[GCC 4.1.1 20070105 (Red Hat 4.1.1-52)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> print sys.version
2.5.2 (r252:60911, Apr 19 2008, 06:33:52)
[GCC 4.1.1 20070105 (Red Hat 4.1.1-52)]
>>> print sys.executable
/usr/local/bin/python2.5
>>>
--~--~-~--~~~---~--~~
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: which python version?

[Valts Mazurs]

Latest stable Python version.
Currently it is Python 2.5.2

Regards,
Valts.

On Thu, May 15, 2008 at 6:03 PM, bcurtu <[EMAIL PROTECTED]> wrote:

>
> Which python version do you use with your django project? Any special
> issue with anyone?
>
> Cheers.
> >
>

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

which python version?

[bcurtu]

Which python version do you use with your django project? Any special
issue with anyone?

Cheers.
--~--~-~--~~~---~--~~
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: Selecting Python version for mod_python

[Graham Dumpleton]

On Apr 10, 1:54 am, Peter Rowell <[EMAIL PROTECTED]> wrote:
> > This means that a python version has to be selected before the PythonPath
> > directive is processed.
>
> "Selected" is not quite the right way to think of it.mod_pythonhas
> the Python interpreter linked in at build time, not run time. To
> change which version you have, you need to rebuildmod_python.
>
> If you are root on this machine:
>
> cd mod_python_directory
> make distclean
> ./configure  --with-python=/path/to/desired/python
> make
> make install

Additionally, that version of 'python' executable must be that which
is found in PATH when Apache is run otherwise it may calculate the
wrong Python library location. If not, need to set PYTHONHOME in
environment Apache uses when run to appropriate Python prefix setting.

Graham
--~--~-~--~~~---~--~~
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: Selecting Python version for mod_python

[Peter Rowell]

> This means that a python version has to be selected before the PythonPath
> directive is processed.

"Selected" is not quite the right way to think of it. mod_python has
the Python interpreter linked in at build time, not run time. To
change which version you have, you need to rebuild mod_python.

If you are root on this machine:

cd mod_python_directory
make distclean
./configure  --with-python=/path/to/desired/python
make
make install
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Selecting Python version for mod_python

[jurian]

How can I go about selecting the python version for mod_python to use?

Using PythonPath doesn't seem to be the way to do this, as stated in
the mod_python documentation, this strign is evaluated. This means
that a python version has to be selected before the PythonPath
directive is processed.
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Python version of Weborb

[[EMAIL PROTECTED]]

I recently emailed the Weborb guys at: http://www.themidnightcoders.com
to see about the possibility of a python version that we could use
with django and he responded like this:

"I would love to add Python to our product line. The biggest challenge
is
finding talent to do it  We do not have any expertise in house, so
we'd need to hire someone. Do you happen to know anyone who might be
available for a fun summer project?"

I thought this would be a good place to pass along the request since a
Python version of this would be great to have! His name is Mark Pillar
and his contact info is on this page :http://www.themidnightcoders.com/
about/

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: FYI: Primitive Python Version of GWT Working

[Siah]

Good work.
Sia


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

FYI: Primitive Python Version of GWT Working

[nkeric]

http://jtauber.com/blog/2006/05/23/primitive_python_version_of_gwt_working

Someone posted this to our site: James Tauber has built "a Python
equivalent to the Google Web Toolkit (GWT)" -
http://code.google.com/webtoolkit

It's interesting :)


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---