Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG: Format and decode errors in Python 2.6 #1506

Merged
merged 1 commit into from Mar 24, 2014

Conversation

Projects
None yet
3 participants
@bashtage
Copy link
Contributor

commented Mar 24, 2014

Fixes two small errors on Python 2.6

  • Improper use of keyword arguments in format, e.g errors='strict'
  • Improper use of position-less format string
Kevin Sheppard
BUG: Format and decode errors in Python 2.6
Fixes two small errors on Python 2.6
- Improper use of keyword arguments in format, e.g errors='strict'
- Improper use of position-less format string
@bashtage

This comment has been minimized.

Copy link
Contributor Author

commented Mar 24, 2014

These were discovered using the Miniconda-Python-2.6 testing. They are very small and the fix passes running against 2.6, see

https://travis-ci.org/bashtage/statsmodels/builds/21408270

jseabold added a commit that referenced this pull request Mar 24, 2014

Merge pull request #1506 from bashtage/python-2-6-fixes
COMPAT: Fix format and decode errors in Python 2.6

@jseabold jseabold merged commit 8d47f53 into statsmodels:master Mar 24, 2014

1 check passed

default The Travis CI build passed
Details

@bashtage bashtage deleted the bashtage:python-2-6-fixes branch Mar 24, 2014

@bashtage bashtage restored the bashtage:python-2-6-fixes branch Mar 24, 2014

@bashtage bashtage deleted the bashtage:python-2-6-fixes branch Mar 24, 2014

@josef-pkt josef-pkt added the PR label Apr 14, 2014

PierreBdR pushed a commit to PierreBdR/statsmodels that referenced this pull request Sep 2, 2014

Merge pull request statsmodels#1506 from bashtage/python-2-6-fixes
COMPAT: Fix format and decode errors in Python 2.6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.