[mezzanine-users] Re: Using Mezzanine with Python 3: package compatibility

2015-05-15 Thread xnx
Thanks Josh and Graham,
I'll stick with PostgreSQL then, but wait until the next Mezzanine release 
before upgrading Django. I'm just glad to have got my site online for now!
Cheers,
Christian

On Friday, May 15, 2015 at 4:31:18 PM UTC-4, Graham Oliver wrote:

 Hi Christian
 In terms of MySQL vs PostgreSQL have a look at 
 https://docs.djangoproject.com/en/1.7/topics/migrations

 When I read
 'PostgreSQL is the most capable of all the databases here in terms of 
 schema support'

 and

 'MySQL lacks support for transactions around schema alteration operations, 
 meaning that if a migration fails to apply you will have to manually unpick 
 the changes in order to try again (it’s impossible to roll back to an 
 earlier point).'

 I decided that PostgreSQL was the best option.

 Cheers
 g

 On Saturday, 16 May 2015 02:32:36 UTC+12, xnx wrote:

 Hello Mezzanine Users,

 I'm new to Mezzanine but not Django: I'm enjoying learning it a lot and 
 it does a great job, but I've run into a couple of problems. I am trying to 
 deploy Mezzanine under Python 3.3.5 and, although I have a working site, I 
 have a couple of questions about compatibility with the packages I need. 
 I'm using Anaconda 2.2.0.

 * Installing Mezzanine with `conda` automatically downgrades my Django 
 version to 1.6.11: is there an upcoming release that will support Django 
 1.7+ under Python 3? I'd like to use django-migrations.

 * Is there any way of using MySQL in this stack? I found I could not 
 install MySQLdb under Python 3 and this seems to be a requirement for 
 Mezzanine using a MySQL backend but isn't provided by Anaconda. I'm using 
 PostgreSQL like a grown-up instead, but my preference would probably be for 
 MySQL.

 * The Mezzanine docs at http://mezzanine.jupo.org/docs/user-accounts.html 
 suggest using AUTH_PROFILE_MODULE to implement user profiles in a 
 Mezzanine site, but  the Django docs at 
 http://django.readthedocs.org/en/latest/releases/1.5.html#auth-profile-module
  
 say that this has been deprecated since 1.5. Am I missing something here?

 Thanks for reading,
 Christian



-- 
You received this message because you are subscribed to the Google Groups 
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[mezzanine-users] Re: Using Mezzanine with Python 3: package compatibility

2015-05-15 Thread Graham Oliver
Hi Christian
In terms of MySQL vs PostgreSQL have a look at 
https://docs.djangoproject.com/en/1.7/topics/migrations

When I read
'PostgreSQL is the most capable of all the databases here in terms of 
schema support'

and

'MySQL lacks support for transactions around schema alteration operations, 
meaning that if a migration fails to apply you will have to manually unpick 
the changes in order to try again (it’s impossible to roll back to an 
earlier point).'

I decided that PostgreSQL was the best option.

Cheers
g

On Saturday, 16 May 2015 02:32:36 UTC+12, xnx wrote:

 Hello Mezzanine Users,

 I'm new to Mezzanine but not Django: I'm enjoying learning it a lot and it 
 does a great job, but I've run into a couple of problems. I am trying to 
 deploy Mezzanine under Python 3.3.5 and, although I have a working site, I 
 have a couple of questions about compatibility with the packages I need. 
 I'm using Anaconda 2.2.0.

 * Installing Mezzanine with `conda` automatically downgrades my Django 
 version to 1.6.11: is there an upcoming release that will support Django 
 1.7+ under Python 3? I'd like to use django-migrations.

 * Is there any way of using MySQL in this stack? I found I could not 
 install MySQLdb under Python 3 and this seems to be a requirement for 
 Mezzanine using a MySQL backend but isn't provided by Anaconda. I'm using 
 PostgreSQL like a grown-up instead, but my preference would probably be for 
 MySQL.

 * The Mezzanine docs at http://mezzanine.jupo.org/docs/user-accounts.html 
 suggest using AUTH_PROFILE_MODULE to implement user profiles in a 
 Mezzanine site, but  the Django docs at 
 http://django.readthedocs.org/en/latest/releases/1.5.html#auth-profile-module 
 say that this has been deprecated since 1.5. Am I missing something here?

 Thanks for reading,
 Christian


-- 
You received this message because you are subscribed to the Google Groups 
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.