I heard about lots of compatibility issues with PostgreSQL and Django + psycopg2.
What would be the recommended latest and greatest versions that are fully compatible for a new Django project starting from scratch?
The bug is not critical: it only affects database creation during tests: https://code.djangoproject.com/ticket/16250 There should be no other problem between psycopg and django.
The problem can be avoided using psycopg 2.4.1, but there have been several bug fixes since then, so I'd rather apply some simple patch to django to make the two play well together.
BTW I wonder when will they release django 1.3.2: the bug is been there for 6 months now...
Related
I am planning to migrate site core 6.5 to site core 8.1. So here i am using below dlls sample
Sitecore.nexus
Sitecore.NVelocity
Sitecore.Analytics
Sitecore.Marketing.Wildcards and etc.
While i am doing POC i got understand Sitecore.Marketing.Wildcards is changed because of vast changes in Rules Engine.I figured out by compile time errors in my code after code has setup with sitecore 8.1. So i planned for another work around.
My question is how can I find a way to discover deprecated or changed functions from one version to another version of site core migrations? I'm trying to fgire this out before I dive into development.
The best way is to go through the release notes and find what is changed.
https://dev.sitecore.net/Downloads/Sitecore%20Experience%20Platform/Sitecore%2081/Sitecore%20Experience%20Platform%2081%20Initial%20Release/Release%20Notes
For example, on the release notes for Sitecore 8.1 on above link, you will find certain deprecated features, functionality, framework like SPEAK 1.1 framework etc. So with every release, some features or components may get deprecated and you need to fix the code break due to this.
I have inherited a Django application that is currently on 1.4 (so no longer officially supported). I am working my way through the Django versions, upgrading the application and obviously many of the libraries used in the application are quite old versions as well.
Is there an easy / standard way to know what versions of a certain library will be compatible with specific Django releases?
Earlier we were using Lucene version 2.3.1.3(Sitecore version 6.5) everything working fine but now we have upgraded to sitecore version 7.0(Initial release) and now we are using Lucene version 3.0.3.0 dll in project.
But now we are not able to compile project because of errors in code file.
Does that means Lucene version 3.0.3.0 dll doesn't support code written in Lucene version 2.3.1.3(Sitecore version 6.5)
Thanks
Upgrading from Sitecore 6.x to 7.0 needs some adjustments in code to get everything work again.
Which error do you get? I also had a specific error regarding lucene dll when compiling after the upgrade but this error was only caused by a wrong assembly redirect in the web.config.
In fact, the search API changed completely and if you made an upgrade to 7.0 it is recommended to update your search logic to the possibilities are now available in 7.0 like LINQ support and so on. Search is much more comfortable now in sitecore 7 and it is really worth taking a closer look at the changes. They took a lot of the advanced database crawler module like dynamic fields (they are now called computed fields) and much more and added it to the sitecore 7 standard search api.
We are just starting some cloud-based apps based on Python + Django and we have a small dilemma. At first we decided to go with Python 3.3, but than we saw that a lot of libraries/modules have not been ported yet, thus we might have to do extra work to make sure that everything works with Python 3.3.
Given the fact that the projects that we are starting will have a time frame of a few years what advice would you give us? To go with Python 2.7 or Python 3.3?
Thanks in advance!
Go with Python 2.7 for now. Make sure that your code translates cleanly when using 2to3. When the modules are available for Python 3.x, translate your code and run with it.
I finally want to migrate a Django project to Python 3.3 but have some issues with django-compressor, because it is not Python 3 compatible (yet).
Out of the asset managers listed on https://www.djangopackages.com/grids/g/asset-managers/ these seem interesting to me, since they support CSS/LESS too:
https://www.djangopackages.com/packages/p/webassets/
https://www.djangopackages.com/packages/p/django-pipeline/
https://www.djangopackages.com/packages/p/django-gears/
I have multiple CSS and LESS files, and a lot of JavaScript files which need to be minified, and Python 3.3 must be supported. What would you recommend for my use case? Are there other, better suited projects around?
I recommend to use a django-pipeline. It supports python 3 and do what it should do. I used it for one of my project ( but it was python 2.7) and perfectly happy with it.