DOC add to_datetime to api.rst
Either I'm being thick or `to_datetime` isn't in the docs (does adding it like this add it?)

Should also put something in basics...?

there should be an example in timeseries.rst and/or basics.rst
but can't remember one
 should be generated by the API docs. grin shows nothing in those that @jreback just mentioned
 @jreback http://pandas.pydata.org/pandas-docs/dev/search.html?q=to_datetime&check_keywords=yes&area=default only result is "what's new".

Should one go in basics or timeseries? (I'd vote for basics.)
 I would put near the top of timeseries (before time spans)
prob could create a separate section (conversions?)
as several options need to be explained, format, day first, tz, 
and a link / mention in basics / dtypes
 Can I include unit ? :)
 yeh...goign to merge that right now in fact......

I think its a reasonable api, yes?
 units defined in  #3818
 @hayd fyi...I believe that `format` option is currentlly ignored, remember that from somewhere...?
 I was worried this was going to be a barrel of worms. maybe there is a reason this function isn't documented... :p
 is it a barrel?
 Nah... putting something together now. (sorry, just got flustered with above issue)
 Also that dayfirst isn't strict. :S
 @jreback @hayd merge?
 I don't think this is ready yet
 k
 It _could_ be merged as is, it would at least get `to_datetime` to the docs.

I've written "something" about using `to_datetime` in tseries api, but not pushed it yet...
 I've done a little more on this, feedback welcome...
 `pd.to_datetime([1, '2'])` is possibly surprising maybe note that?
 `dateutil` defaults on making a date string of just an integer midnight on the current day iirc
 @cpcloud woah! I'd never done: `pd.to_datetime(['2'])`, er!! Will add it in.
 That is also strange, and the thing which means that `to_datetime` isn't just `map(Timestamp, x)`, I dislike examples where it isn't (but they need to be included).
 this is good!

see #3890, which resolves almost all of the inconsistencies
 Ah cool! Didn't realise hasn't been merged yet! :)
 This is still whacky:
 ```
In [4]: pd.to_datetime([1, '1'])
Out[4]:
<class 'pandas.tseries.index.DatetimeIndex'>
[1970-01-01 00:00:00.000000001, 2013-06-01 00:00:00]
Length: 2, Freq: None, Timezone: None
```

so will mention it
 not sure there's any other way to go about it. need to use ints for representation but want to be able to parse semi human readable dates and `int`s...dateutil is _extremely_ lenient except e.g., it won't parse an `int`. hopefully no one is abusing pandas in this way
 can u add that last to #3944?

I think we are all agreed that the default to_ datetime should be more strict
 done
 that why I separated out #3944 

dateutil lets everything thru

so have to do some most common case parsing first

need to expand c date parser then can pretty much drop need for dateutil except as fallback
 (and it's not strict for dayfirst grrr!)
