<p dir="auto">I am using <code class="notranslate">pandas.__version__==0.14.0</code>.<br>
This is my first bug report in github so excuse my possibly poorly formatted submission.</p>
<p dir="auto">This bug report might be related to, or duplicate:</p>
<ol dir="auto">
<li><a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="9712660" data-permission-text="Title is private" data-url="https://github.com/pandas-dev/pandas/issues/2646" data-hovercard-type="issue" data-hovercard-url="/pandas-dev/pandas/issues/2646/hovercard" href="https://github.com/pandas-dev/pandas/issues/2646">#2646</a></li>
<li><a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="28467007" data-permission-text="Title is private" data-url="https://github.com/pandas-dev/pandas/issues/6501" data-hovercard-type="issue" data-hovercard-url="/pandas-dev/pandas/issues/6501/hovercard" href="https://github.com/pandas-dev/pandas/issues/6501">#6501</a></li>
</ol>
<p dir="auto">It was explained to me by [http://stackoverflow.com/users/1427416/brenbarn] on the following StackOverflow question, <a href="http://stackoverflow.com/questions/24683023/having-issue-with-hierarchical-index-set-behavior/24684844#24684844" rel="nofollow">http://stackoverflow.com/questions/24683023/having-issue-with-hierarchical-index-set-behavior/24684844#24684844</a></p>
<p dir="auto">Essentially,  the following behavior is not desirable:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="print pd.__version__
WeirdIdx = pd.MultiIndex(levels=[[0], [1]],labels=[[0, 0], [0,0]],names=[u'X', u'Y'])
print WeirdIdx
print (0, 0) in WeirdIdx
print (1, 0) in WeirdIdx
print (100, 0) in WeirdIdx
print (100, 100) in WeirdIdx"><pre class="notranslate"><code class="notranslate">print pd.__version__
WeirdIdx = pd.MultiIndex(levels=[[0], [1]],labels=[[0, 0], [0,0]],names=[u'X', u'Y'])
print WeirdIdx
print (0, 0) in WeirdIdx
print (1, 0) in WeirdIdx
print (100, 0) in WeirdIdx
print (100, 100) in WeirdIdx
</code></pre></div>
<p dir="auto">since it prints:<br>
0.14.0<br>
X  Y<br>
0  1<br>
1<br>
True<br>
True<br>
True<br>
True</p>
<p dir="auto">despite the fact that <code class="notranslate">(100,0)</code> and <code class="notranslate">(100,100)</code> are unambiguously not part of the index.</p>
<p dir="auto">Timestamp stores the value in a <code class="notranslate">datetime64[ns]</code> internal representation. For most purposes this is fine, but I'd love if I could choose the internal precision, for example to use <code class="notranslate">datetime64[s]</code> instead.</p>
<p dir="auto">When I do timeseries manipulations that span more than a day, I generally do not need sub-second resolution and I could definitely use the extended range instead. But, more conveniently, this would also allow to pretty-print the result without a ton of trailing zeros without setting some arbitrary threshold.</p>
<p dir="auto">Incidentally, this would remove the limit of ~500 years, but it's more of an ergonomic change than an actual need. For example, when I need to perform direct manipulations of the values in a DatetimeIndex, I often have to scale up to seconds if I want to perform meaningful fitting and avoid numerical instability. When plotting, it's an extra indirection I need to care about.</p>