Skip to content

Conversation

@techdragon
Copy link

Test against python 3.4, all the cool kids are doing it. ;-)

Test against python 3.4, all the cool kids are doing it. ;-)
@theju
Copy link
Contributor

theju commented Jan 27, 2015

Started the process of migrating to Py3 but there are a few roadblocks:

  • Suds used by EPay is not supported on Py3
  • WePay python sdk is not supported on Py3
  • FormEncode used for travis is not supported on Py3
  • Some instances of Py2 code in the merchant code base (these are being removed as and when we come across).

I don't think we are inclined to go the route of forking these packages and maintaining them.

@tuxcanfly
Copy link
Member

FormEncode is only a util for the build process, but suds and wepay sound like major bottlenecks.

@theju
Copy link
Contributor

theju commented Jan 27, 2015

@tuxcanfly That's right but would be great to have your opinion on continuing with Travis.

@tuxcanfly
Copy link
Member

There are too many external variables affecting the tests, lets put open issues and features on top priority and get back to travis later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants