Skip to content

Conversation

@vmarkovtsev
Copy link
Contributor

As described in #84

@vmarkovtsev
Copy link
Contributor Author

I see that it breaks 2.6. Unable to test it, unfortunately.

@gmr
Copy link
Owner

gmr commented Dec 8, 2015

Thanks for that, would you mind resubmitting with only the timeout changes and split out the locale change to a new PR along with the bug fix in the rabbitpy/amqp? It makes it easier to track that way.

Also your PR breaks in both Python 2.6 and 3.2.

@vmarkovtsev
Copy link
Contributor Author

done. Python 3.2 seems to be broken before my edits.

@vmarkovtsev
Copy link
Contributor Author

If you take a look at the error, it is in coverage package, which clearly states that it does not support python 3.2. It used to support it, perhaps, but you forgot to freeze the versions in your requirements file.

@eandersson
Copy link

@gmr You need to add something like this for Coverage to work with Python 3.2, or don't use Coverage 4.x at all. =]

 - if [[ $TRAVIS_PYTHON_VERSION == '3.2' ]]; then pip install coverage==3.7.1; fi

canardleteer added a commit to canardleteer/rabbitpy that referenced this pull request Feb 27, 2016
canardleteer pushed a commit to canardleteer/rabbitpy that referenced this pull request Mar 10, 2016
- AMQP.basic_publish() would spit out the following:
  ValueError: channel must be a valid rabbitpy Channel object
  This is resolved and added to the unit tests.
- Coverage patch for Travis-CI (from @eandersson: gmr#85)
@gmr gmr merged commit 3a22f99 into gmr:master Mar 29, 2016
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