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

DOC: Remove old warning from dsintro.rst #14365

Merged
merged 1 commit into from
Oct 6, 2016

Conversation

Tarrasch
Copy link
Contributor

@Tarrasch Tarrasch commented Oct 6, 2016

  • closes #xxxx
  • tests added / passed
  • passes git diff upstream/master | flake8 --diff
  • whatsnew entry

The warning is about something that have been fixed for almost 3 years. Every time a new user excited about pandas start reading the docs, they have to waste brain-cycles ignoring that big red warning bubble.

The warning is about something that have been fixed for almost 3 years. Every time a new user excited about pandas start reading the docs, they have to waste brain-cycles ignoring that big red warning bubble.
@Tarrasch Tarrasch changed the title docs: Remove old warning from dsintro.rst DOC: Remove old warning from dsintro.rst Oct 6, 2016
@jorisvandenbossche jorisvandenbossche added this to the 0.19.1 milestone Oct 6, 2016
@jorisvandenbossche
Copy link
Member

Yes, good idea! Thanks

@jorisvandenbossche jorisvandenbossche merged commit 507e037 into pandas-dev:master Oct 6, 2016
@Tarrasch Tarrasch deleted the patch-1 branch October 6, 2016 10:19
@jreback
Copy link
Contributor

jreback commented Oct 6, 2016

actually could prob take out the Index warning as well (indexing.rst). Maybe also look for older things like this elsewhere.

@Tarrasch
Copy link
Contributor Author

Tarrasch commented Oct 6, 2016

Thanks for the quick merge @jorisvandenbossche . This certainly encourages me to keep sending patches like this. :)

@jreback, absolutely. This is my first touch in the code base, so I won't take on that endeavor. But if this inspires a maintainer to do it. I would be ever so glad. :)

@jorisvandenbossche
Copy link
Member

Yes, I think we should do a general search on version notices below 0.15 or so (also for notices that something was added in eg version 0.14 -> although maybe we could leave that for the 1.0 docs to do a big cleanup)

@TomAugspurger
Copy link
Contributor

Also removing the "experimental" tags on some sections if they're ready

@jorisvandenbossche
Copy link
Member

Regarding experimental, there is an issue for that: #5049

yarikoptic added a commit to neurodebian/pandas that referenced this pull request Oct 13, 2016
* commit 'v0.19.0-14-ga40e185': (37 commits)
  BUG: Bug in localizing an ambiguous timezone when a boolean is passed
  Convert readthedocs links for their .org -> .io migration for hosted projects (pandas-dev#14406)
  DOC: formatting in basics.rst
  BLD/CI: cython cache pxd files (pandas-dev#14363)
  BUG: set_levels set illegal levels. (pandas-dev#14236)
  DOC: add whitespace to v0.19.1 bug fix section
  change impl details slightly for pandas-dev#14292
  BUG: Fix concat key name
  DOC: add 0.19.1 whatsnew file (pandas-dev#14366)
  DOC: to_csv warns regarding quoting behaviour for floats pandas-dev#14195 (pandas-dev#14228)
  DOC: fix formatting issue with msgpack table
  TST: pandas-dev#14345 fixes TestDatetimeIndexOps test_nat AssertionErrors on 32-bit
  docs: Remove old warning from dsintro.rst (pandas-dev#14365)
  DOC: minor v0.19.0 whatsnew corrections
  RLS: v0.19.0
  DOC: update release notes
  DOC: Latest fixes for whatsnew file
  to_latex encoding follows the documentation (py2 ascii, py3 utf8) (pandas-dev#14329)
  DOC: fix some sphinx build issues (pandas-dev#14332)
  TST: fix period tests for numpy 1.9.3 (GH14183) (pandas-dev#14331)
  ...
tworec pushed a commit to RTBHOUSE/pandas that referenced this pull request Oct 21, 2016
The warning is about something that have been fixed for almost 3 years. Every time a new user excited about pandas start reading the docs, they have to waste brain-cycles ignoring that big red warning bubble.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants