This file is indexed.

/usr/share/doc/py3c-dev/html/index.html is in py3c-dev 1.0-1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
<!DOCTYPE html>
<!--[if IE 8]><html class="no-js lt-ie9" lang="en" > <![endif]-->
<!--[if gt IE 8]><!--> <html class="no-js" lang="en" > <!--<![endif]-->
<head>
  <meta charset="utf-8">
  
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  
  <title>py3c: Python 2/3 compatibility layer for C extensions &mdash; py3c 1.0a1 documentation</title>
  

  
  
  
  

  

  
  
    

  

  
  
    <link rel="stylesheet" href="_static/css/theme.css" type="text/css" />
  

  

  
        <link rel="index" title="Index"
              href="genindex.html"/>
        <link rel="search" title="Search" href="search.html"/>
    <link rel="top" title="py3c 1.0a1 documentation" href="#"/>
        <link rel="next" title="Porting guide for Python C Extensions" href="guide.html"/> 

  
  <script src="_static/js/modernizr.min.js"></script>

</head>

<body class="wy-body-for-nav" role="document">

   
  <div class="wy-grid-for-nav">

    
    <nav data-toggle="wy-nav-shift" class="wy-nav-side">
      <div class="wy-side-scroll">
        <div class="wy-side-nav-search">
          

          
            <a href="#" class="icon icon-home"> py3c
          

          
          </a>

          
            
            
              <div class="version">
                1.0
              </div>
            
          

          
<div role="search">
  <form id="rtd-search-form" class="wy-form" action="search.html" method="get">
    <input type="text" name="q" placeholder="Search docs" />
    <input type="hidden" name="check_keywords" value="yes" />
    <input type="hidden" name="area" value="default" />
  </form>
</div>

          
        </div>

        <div class="wy-menu wy-menu-vertical" data-spy="affix" role="navigation" aria-label="main navigation">
          
            
            
              
            
            
              <ul>
<li class="toctree-l1"><a class="reference internal" href="guide.html">Porting guide for Python C Extensions</a></li>
<li class="toctree-l1"><a class="reference internal" href="cheatsheet.html">The py3c Cheatsheet</a></li>
<li class="toctree-l1"><a class="reference internal" href="defs.html">Definitions in py3c</a></li>
<li class="toctree-l1"><a class="reference internal" href="reference.html">py3c reference</a></li>
<li class="toctree-l1"><a class="reference internal" href="special-guides.html">Special Porting Guides</a></li>
<li class="toctree-l1"><a class="reference internal" href="contributing.html">Contributing to py3c</a></li>
<li class="toctree-l1"><a class="reference internal" href="changelog.html">py3c Changes</a></li>
</ul>

            
          
        </div>
      </div>
    </nav>

    <section data-toggle="wy-nav-shift" class="wy-nav-content-wrap">

      
      <nav class="wy-nav-top" role="navigation" aria-label="top navigation">
        
          <i data-toggle="wy-nav-top" class="fa fa-bars"></i>
          <a href="#">py3c</a>
        
      </nav>


      
      <div class="wy-nav-content">
        <div class="rst-content">
          















<div role="navigation" aria-label="breadcrumbs navigation">

  <ul class="wy-breadcrumbs">
    
      <li><a href="#">Docs</a> &raquo;</li>
        
      <li>py3c: Python 2/3 compatibility layer for C extensions</li>
    
    
      <li class="wy-breadcrumbs-aside">
        
            
            <a href="_sources/index.rst.txt" rel="nofollow"> View page source</a>
          
        
      </li>
    
  </ul>

  
  <hr/>
</div>
          <div role="main" class="document" itemscope="itemscope" itemtype="http://schema.org/Article">
           <div itemprop="articleBody">
            
  <div class="section" id="py3c-python-2-3-compatibility-layer-for-c-extensions">
<h1>py3c: Python 2/3 compatibility layer for C extensions<a class="headerlink" href="#py3c-python-2-3-compatibility-layer-for-c-extensions" title="Permalink to this headline"></a></h1>
<p>This is <em>py3c</em>, a library for easing porting C extensions to Python 3,
providing macros for <em>single-source compatibility</em> between
Python 2.6, 2.7, and 3.3+.
It could be described as “the <a class="reference external" href="https://pypi.python.org/pypi/six">six</a>
for C extensions”.</p>
<p>Pick the docs you wish to read:</p>
<ul>
<li><p class="first"><a class="reference internal" href="guide.html"><span class="doc">Porting guide</span></a></p>
<blockquote>
<div><p>A detailed <strong>walkthrough</strong> for porting to Python 3.
Read if you wish to start porting a C extension to Python 3.</p>
</div></blockquote>
</li>
<li><p class="first"><a class="reference internal" href="cheatsheet.html"><span class="doc">Cheatsheet</span></a></p>
<blockquote>
<div><p>A <strong>quick reference</strong>, helpful if you’re in the middle of porting.
Also useful if you find yourself working on a project that someone else
is porting, and don’t understand what’s going on.</p>
<p>If you want something to print out a stick on your wall,
use this – compared to the other docs, you’ll save trees.</p>
</div></blockquote>
</li>
<li><p class="first"><a class="reference internal" href="defs.html"><span class="doc">Definition Summary</span></a></p>
<blockquote>
<div><p>A <strong>table</strong> summarizing how py3c’s macros are defined.
Convenient if you already know the differences between Python 2 and 3,
or before a dive into py3c’s internals.</p>
<p>Also serves as a summary of where py3c provides the
Python 3 API, and where it resorts to inventing its own macros.</p>
</div></blockquote>
</li>
<li><p class="first"><a class="reference internal" href="reference.html"><span class="doc">Reference</span></a></p>
<blockquote>
<div><p>Lists <strong>every macro</strong> py3c defines.
The search will point you here when it finds a term.</p>
</div></blockquote>
</li>
<li><p class="first"><a class="reference internal" href="genindex.html"><span class="std std-ref">Index</span></a> and <a class="reference internal" href="search.html"><span class="std std-ref">Search</span></a></p>
<blockquote>
<div><p>Head here if you’re looking for something specific.</p>
</div></blockquote>
</li>
</ul>
</div>
<div class="section" id="project-info">
<h1>Project info<a class="headerlink" href="#project-info" title="Permalink to this headline"></a></h1>
<p>The py3c library is available under the MIT license.
This documentation is available under the Creative Commons Attribution-ShareAlike 3.0 Unported license.
May they serve you well.</p>
<p>The high-level history of py3c is chronicled in the <a class="reference internal" href="changelog.html"><span class="doc">Changelog</span></a>.</p>
<p>If you’d like to contribute code, words, suggestions, bug reports, or anything else,
do so at <a class="reference external" href="http://github.com/encukou/py3c">the Github page</a>.
For more info, see <a class="reference internal" href="contributing.html"><span class="doc">Contributing</span></a>.</p>
<p>Oh, and you should pronounce “py3c” with a hard “c”, if you can manage to do so.</p>
<div class="toctree-wrapper compound">
</div>
</div>


           </div>
           <div class="articleComments">
            
           </div>
          </div>
          <footer>
  
    <div class="rst-footer-buttons" role="navigation" aria-label="footer navigation">
      
        <a href="guide.html" class="btn btn-neutral float-right" title="Porting guide for Python C Extensions" accesskey="n" rel="next">Next <span class="fa fa-arrow-circle-right"></span></a>
      
      
    </div>
  

  <hr/>

  <div role="contentinfo">
    <p>
        &copy; Copyright 2018, Red Hat, Inc. and/or its affiliates.

    </p>
  </div>
  Built with <a href="http://sphinx-doc.org/">Sphinx</a> using a <a href="https://github.com/snide/sphinx_rtd_theme">theme</a> provided by <a href="https://readthedocs.org">Read the Docs</a>. 

</footer>

        </div>
      </div>

    </section>

  </div>
  


  

    <script type="text/javascript">
        var DOCUMENTATION_OPTIONS = {
            URL_ROOT:'./',
            VERSION:'1.0a1',
            COLLAPSE_INDEX:false,
            FILE_SUFFIX:'.html',
            HAS_SOURCE:  true,
            SOURCELINK_SUFFIX: '.txt'
        };
    </script>
      <script type="text/javascript" src="_static/jquery.js"></script>
      <script type="text/javascript" src="_static/underscore.js"></script>
      <script type="text/javascript" src="_static/doctools.js"></script>

  

  
  
    <script type="text/javascript" src="_static/js/theme.js"></script>
  

  
  
  <script type="text/javascript">
      jQuery(function () {
          SphinxRtdTheme.StickyNav.enable();
      });
  </script>
   

</body>
</html>