-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
DOC: Spellcheck of gotchas.rst (FAQ page) #19747
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
Codecov Report
@@ Coverage Diff @@
## master #19747 +/- ##
==========================================
- Coverage 91.6% 91.6% -0.01%
==========================================
Files 150 150
Lines 48908 48864 -44
==========================================
- Hits 44804 44763 -41
+ Misses 4104 4101 -3
Continue to review full report at Codecov.
|
would welcome this an additional check in the lint.sh |
doc/source/gotchas.rst
Outdated
|
||
.. ipython:: python | ||
|
||
dtypes = ['int64', 'float64', 'datetime64[ns]', 'timedelta64[ns]', | ||
'complex128', 'object', 'bool'] | ||
n = 5000 | ||
data = dict([ (t, np.random.randint(100, size=n).astype(t)) | ||
data = dict([(t, np.random.randint(100, size=n).astype(t)) | ||
for t in dtypes]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you fix indent here
specifies if the dataframe's memory usage will be displayed when | ||
invoking the ``df.info()`` method. | ||
The memory usage of a ``DataFrame`` (including the index) is shown when calling | ||
the :meth:`~DataFrame.info`. A configuration option, ``display.memory_usage`` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you reference this option directly?
doc/source/gotchas.rst
Outdated
@@ -320,7 +323,7 @@ a different byte order than the one on which you are running Python. A common sy | |||
|
|||
To deal | |||
with this issue you should convert the underlying NumPy array to the native | |||
system byte order *before* passing it to Series/DataFrame/Panel constructors | |||
system byte order *before* passing it to ``Series``/``DataFrame`` constructors |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/ -> or
There are certain legitimate use cases of |
For example, the code snippet here is done with a bar |
ci/lint.sh
Outdated
@@ -149,6 +149,15 @@ if [ "$LINT" ]; then | |||
RET=1 | |||
fi | |||
echo "Check for deprecated messages without sphinx directive DONE" | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does this pass now?
small question. looks fine. can you rebase and push again just to make sure. |
Ah, I didn't see that the CI was passing. But since we still have occurrences of |
I believe this PR is good to go now. Thanks for double-checking the lint @jorisvandenbossche. It seems like it was not working, glad you caught it. Since there might be cases which warrant |
I guess, but why can't we cross this bridge i its actually needed. not-specifying python makes this look not so great and easy enough to avoid with a lint check. |
The cases of But as I mentioned above, there are other cases where this was done on purpose (#19747 (comment)). And in those they are currently rendered fine. I am not sure if those cases are actually needed, but if someone wants to remove them, we should first check the docs build correctly without them. |
ok that’s fine |
Minor changes to the documentation, specifically
gotchas.rst
, i.e. the FAQ page.``
around Series, DataFrame... ipython::
withipython:: python
twice, as the former is not sufficient to make the iPython code render in the docs.Reviews/comments very welcome.