I've migrated to using django-payments on most of the websites I maintain for over a year now.
It's generally better designed, and has the upside of supporting multiple payment processors.
Because of this, I won't really be maintaining this library much any more -- I'd recommend looking at django-payments if you're getting started on a new project.
django-mercadopago currently works with the latest version of Django, and should continue working fine for the next couple of releases too. I'll accept PRs for bugfixes, and if anyone needs to continue using this library and wants to adopt it, I'm open to that too. However, I would recommend looking at django-payments, since having two libraries which can achieve the same thing is a bit of wasted/duplicate effort.
I've migrated to using django-payments on most of the websites I maintain for over a year now.
It's generally better designed, and has the upside of supporting multiple payment processors.
Because of this, I won't really be maintaining this library much any more -- I'd recommend looking at django-payments if you're getting started on a new project.
django-mercadopago currently works with the latest version of Django, and should continue working fine for the next couple of releases too. I'll accept PRs for bugfixes, and if anyone needs to continue using this library and wants to adopt it, I'm open to that too. However, I would recommend looking at django-payments, since having two libraries which can achieve the same thing is a bit of wasted/duplicate effort.