Hacker News new | past | comments | ask | show | jobs | submit login

The release notes can be found at https://docs.djangoproject.com/en/1.6/releases/1.6/

Personally, I'm happy that Python 3 is now officially supported, though in practice I haven't had an issues with using Django 1.5 with Python 3.




How is library support? I didn't have any issues with django 1.5 itself, but many of my favorite libraries weren't ready yet.


Django Packages lists 160 apps that work with Python 3. See https://www.djangopackages.com/python3/

From personal experience, most of the critical ones are compatible.


Boto (using SES for email) is main one. And supervisord if you want to keep your deployment Python 3 only.


https://github.com/boto/boto3

Still in progress, but there you go.


Circus is Python 3 compatible if people are looking for an alternative to supervisor.

There's always the option of just using Upstart or systemd as well.


Circus looks huge and doesn't appeal for one or two apps. I do however wish to experiment with circus at some point. Do you have any comparison to make, assuming you have used both? Or anyone out there? Thanks


I think the MySQL one might be quite a big one for many people. I know Postgress is better (South tells me every time the migration doesn´t work) but for converting older projects it definitely going to be useful.


Well, apart from Fabric.


You may want to check out Invoke (https://github.com/pyinvoke/invoke); it's the successor to Fabric, and it's Python 3 compatible.


For what I can see, Invoke is just a revamped version of Fabric’s task running components. Fabric 2.0 will "leverage Invoke for task running, leaving Fabric itself much more library oriented".


HN appended that link: https://github.com/pyinvoke/invoke


Fabric is on the way. Paramiko, the ssh library underlying Fabric, now has a Python 3 PR for which all tests pass: https://github.com/paramiko/paramiko/pull/233


Fabric isn't part of Django. There is nothing specific about Django in Fabric. In fact, the vast majority of my deployments do not use Fabric.


I am aware of that, but I still consider it one of my favorite libraries, and thought it would be useful to mention that it's not yet py3k-ready. I can imagine quite a few people might depend on it. What are you using instead?


Do you use something in place of Fabric?


Paramiko could be a good example i think...


I was thinking something more like ansible.

Of course I'm partial to my new pave project: https://bitbucket.org/mixmastamyk/pave It is based on fabric, and uses a yaml file to automate it.


No, no, fabric uses paramiko as the ssh abstraction layer.


And reportlab


Last I looked reportlab doesn't even use new-style classes.


Here's a useful site showing Py3 support for packages: https://python3wos.appspot.com


The standard MySQL driver wasn´t working the other day when I tried. That might be quite a big one for some people. I saw you could apply a patch, but I didn´t get round to trying yet.


Alpha release of Oracle MySQL Connector/Python http://dev.mysql.com/downloads/connector/python/ actually works with Django 1.5+ and Python3. But you will be on the bleeding edge if you put it in production.


You could also try this: https://pypi.python.org/pypi/PyMySQL




Applications are open for YC Summer 2019

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: