-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
Pandas different between Python 2.7 and Python 3.5 #16380
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
Comments
on py3
These construct differently in py2 and py3 as range is a list in py2 (and an actual range object).
|
that said this path is only lightly tested. so prob not propagating the name properly. a pull-request to fix welcomed! |
Going to work on this issue at the pycon sprint |
Removing the A PR still welcome though. |
This looks to work on master. Could use a test
|
Code Sample, a copy-pastable example if possible
Problem description
On Python 2.7, the above code results in:
while on Python 3.5, the same code results in:
I see this difference between Python 2 and 3 for pandas 0.18.0, 0.19.2, and 0.20.1.
Expected Output
Or at least consistency.
Output of
pd.show_versions()
pandas: 0.18.0
nose: 1.3.7
pip: 8.1.2
setuptools: 27.2.0
Cython: 0.24.1
numpy: 1.10.4
scipy: 0.18.1
statsmodels: 0.6.1
xarray: None
IPython: 5.1.0
sphinx: 1.4.6
patsy: 0.4.1
dateutil: 2.5.3
pytz: 2016.6.1
blosc: None
bottleneck: 1.1.0
tables: 3.2.2
numexpr: 2.6.1
matplotlib: 1.5.3
openpyxl: 2.3.2
xlrd: 1.0.0
xlwt: 1.1.2
xlsxwriter: 0.9.3
lxml: 3.6.4
bs4: 4.5.1
html5lib: None
httplib2: None
apiclient: None
sqlalchemy: 1.0.13
pymysql: None
psycopg2: None
jinja2: 2.8
boto: 2.42.0
The text was updated successfully, but these errors were encountered: