# python 3 compatibility, etc.

**URL:** <https://discourse.citationstyles.org/t/python-3-compatibility-etc/518>\
**Category:** CSL Development\
**Created:** [December 7, 2008, 7:37pm UTC](https://discourse.citationstyles.org/t/python-3-compatibility-etc/518 "2008-12-07T19:37:59Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bruce\_D\_Arcus1](https://avatars.discourse-cdn.com/v4/letter/b/4bbf92/32.png) [@Bruce\_D\_Arcus1](https://discourse.citationstyles.org/u/Bruce_D_Arcus1)\
**Post date:** [December 7, 2008, 7:37pm UTC](https://discourse.citationstyles.org/t/python-3-compatibility-etc/518/1 "2008-12-07T19:37:59Z")

</div>

In case anyone is thinking about citeproc-py, this seems like a useful  
overview of how to manage compatibility with the new Python 3.

[http://lucumr.pocoo.org/cogitations/2008/12/07/porting-to-python-3-dos-and-donts/](http://lucumr.pocoo.org/cogitations/2008/12/07/porting-to-python-3-dos-and-donts/)

It seems the basic suggestion is just to make sure that your code can  
be automatically converted to being 3-compliant (using the 2to3 tool),  
and to avoid py.test.

Bruce