-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
CLN: Fix CRLFs in repo + add .gitattributes #3915
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
Conversation
Looks like it's not a huge deal in re core/expressions - it's all @jreback and looks like only 3 commits total https://github.com/jtratner/pandas/blame/8bde194aef964ff4294271bbf9da587f144ab9bd/pandas/core/expressions.py . More of a loss in 10 minutes to pandas section - https://github.com/pydata/pandas/blame/d1556237eee69aaeee47a4d1014f782413ad2d7f/doc/source/10min.rst |
yep that was before changed my git settings to not update line endings |
@jreback Well, this would prevent this from occurring with anyone else's contributions. |
👍 on this because this gets annoying sometimes when a script barfs the oh-so-cryptic |
did u do a doc build? |
@cpcloud ? do you mean check if this builds docs okay? |
yep sorry didn't mean to be so terse |
i can do it if u want |
it's no problem...made me install pytables and hdf5 anyways :) took me a On Sun, Jun 16, 2013 at 7:56 PM, Phillip Cloud [email protected]:
|
there's a json error but i'm not sure if that's from here it might be fixed after u rebase. try it and c |
well not error but "invalid" sphinx |
oh what is the |
FYI I think the doc string is screwed up somehow in read_json which is causing that sphix error |
@cpcloud I was trying to figure out why I was getting CRLF errors all over the place, so I explored and found that somewhere. Okay, I need to redo this off of master (going to keep it on the same branch name though). Give me a minute. |
Which file is that? I can probably fix it. On Sun, Jun 16, 2013 at 8:08 PM, jreback [email protected] wrote:
|
iirc pandas.io.json |
word of caution, the 11.0 release raised issues with pickle files being detected as text xref #3360 |
problem in json docstring is nested lists, not sure exactly where but if u nest u need to separate each node from its children by a newline |
@y-p added that and rebased. On Sun, Jun 16, 2013 at 9:06 PM, Phillip Cloud [email protected]:
|
@cpcloud not going to try to fix this for this commit, given that the issue On Sun, Jun 16, 2013 at 9:15 PM, Jeffrey Tratner
|
i fixed it already. was just merged #3930 |
@jtratner can u rebase? (just did a doc build and it was fine). will merge after the rebase... |
btw i just saw the blames at the top i had no idea about this feature of gh. kind of cool |
@cpcloud that's a git feature too (github makes it look nicer though), On Sun, Jun 16, 2013 at 10:43 PM, Phillip Cloud [email protected]:
|
i like git blame but it's a bit ugly. i'm sure there are ways to make it pretty but i don't use it that often... |
any objections to merging this? |
@jtratner sorry 2 be a pain but what about adding lines in |
so that would be
i think |
stata is |
Okay, that's done. Not going to squash b/c it's time consuming. |
should be ok not to rebase, just 3 commits here. |
I'll do it after work tonight.
|
looks good 2 me. |
ok here too.... |
CLN: Fix CRLFs in repo + add .gitattributes
thank you @jtratner |
@jreback @cpcloud @y-p et al - if you have issues rebasing on to master after this because of the line endings (should really only come into play if you were changing git rebase <branch> -s recursive -X renormalize and this will make git ignore the differences in line endings. Thanks to this SO answer for the solution! |
that is a nice solution, maybe i will webscrape pandas github repo using pandas' own |
View this pull request with
?w=t
added to the end of the url to see that there are not differences [aside from the .gitattributes files] - this should prevent more commits with CRLF entering the repo.I think it'd be good to merge this (especially because we can avoid this happening in the future.), though (I think) it'll mess up the history for 10 minutes to pandas and
pandas/core/expressions.py
.After this, will never need to deal with CRLF again! Yay!