search

sukri12 / pysal

Automatically exported from code.google.com/p/pysal
Other
0 stars 0 forks source link

implement PEP #9 #151

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Task to be completed

http://pysal.org/1.2/developers/pep/pep-0009.html

Original issue reported on code.google.com by phil.stp...@gmail.com on 13 Apr 2011 at 10:22

GoogleCodeExporter commented 8 years ago 
The 2to3 tool can automagically assist in this transition.

estrella:wiki stephens$ 2to3 --help
Usage: 2to3 [options] file|dir ...

Options:
  -h, --help            show this help message and exit
  -d, --doctests_only   Fix up doctests only
  -f FIX, --fix=FIX     Each FIX specifies a transformation; default: all
  -j PROCESSES, --processes=PROCESSES
                        Run 2to3 concurrently
  -x NOFIX, --nofix=NOFIX
                        Prevent a fixer from being run.
  -l, --list-fixes      List available transformations
  -p, --print-function  Modify the grammar so that print() is a function
  -v, --verbose         More verbose logging
  --no-diffs            Don't show diffs of the refactoring
  -w, --write           Write back modified files
  -n, --nobackups       Don't write backups for modified files.

Original comment by phil.stp...@gmail.com on 13 Apr 2011 at 10:23

GoogleCodeExporter commented 8 years ago

Original comment by schmi...@gmail.com on 14 Apr 2011 at 12:17

GoogleCodeExporter commented 8 years ago

Original comment by phil.stp...@gmail.com on 20 Apr 2011 at 7:18

GoogleCodeExporter commented 8 years ago 
Plan of attack:
-Sprint session dedicated to porting pysal to 2.6 and 3.0 compatibility
-After the porting all future commits need to be 2.6 and 3.0 compatible
-Need to change tests for this

Original comment by dfo...@gmail.com on 19 May 2011 at 7:04

GoogleCodeExporter commented 8 years ago 
Wait until we support 2.7 as a minimum

Original comment by sjsrey on 7 Oct 2011 at 7:36

GoogleCodeExporter commented 8 years ago 
It appears to me that Scipy supports python3 by dynamically writing 
python3-compatible files as needed. They have a tool in scipy/tools/py3tool.py  
that runs the 2to3 tool and generates the new modules to be run alongside the 
existing modules.  In effect, they're running two code bases, not a single one.

Original comment by phil.stp...@gmail.com on 13 Feb 2012 at 6:09

GoogleCodeExporter commented 8 years ago 
While PySAL is now dynamically refactored on installation into Python3, issues 
remain with FileIO and possibly other tests. Attached is pysal 3 test output 
using defaults from the trunk files setup.cfg and nose-exclude.txt.

Original comment by phil.stp...@gmail.com on 20 Feb 2012 at 10:44

GoogleCodeExporter commented 8 years ago 
Updated results attached.

Original comment by phil.stp...@gmail.com on 21 Feb 2012 at 10:15

GoogleCodeExporter commented 8 years ago 
Updated results attached. Passed in "ulimit -S -n 1024" to overcome open file 
limit on OSX prior to this run, to eliminate related test failures.

Original comment by phil.stp...@gmail.com on 21 Feb 2012 at 10:21

Attachments:

GoogleCodeExporter commented 8 years ago 
Check FileIO, bytes issues.

Original comment by schmi...@gmail.com on 1 May 2012 at 8:48

GoogleCodeExporter commented 8 years ago

Original comment by schmi...@gmail.com on 13 Jul 2012 at 6:15

GoogleCodeExporter commented 8 years ago 
Issue 234 has been merged into this issue.

Original comment by schmi...@gmail.com on 11 Jan 2013 at 2:23

GoogleCodeExporter commented 8 years ago 
https://www.ibm.com/developerworks/linux/library/l-python3-1/

setting a higher priority, pushing for 1.6

Original comment by phil.stp...@gmail.com on 11 Jan 2013 at 4:40

GoogleCodeExporter commented 8 years ago

Original comment by phil.stp...@gmail.com on 29 Jan 2013 at 8:42