-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python3 support? #48
Comments
I merged a pull request a few days ago that begins python 3 support. Unit tests are passing under both python 2 and 3. Included scripts are failing. |
I will publish a new release to pypi when python 3 support is complete. |
Is Python 3 support still in the works, or is it something I would need to take on myself? Thanks! |
Maybe related to Python 3 support, but when I tried running the validator against the example file, I got an error:
|
I had the same problem - changing the following starting at line 90 in x12valid.py solved it for me: + if args.verbose is not None and type(args.verbose).__name__ == 'int':
- if args.verbose > 0:
- logger.setLevel(logging.DEBUG)
+ if args.verbose > 0:
+ logger.setLevel(logging.DEBUG) Python 3 has changes regarding to None and ordering comparisons, basically any None types are no longer equivalent to 0. See: Python 3 - What's new - Ordering Comparisons @azoner @rubic |
Is this still open? Giving a first pass on this but don't see much documentation. I made the change mentioned by @ddw360 but getting a different error. Would love to contribute to this project. |
The py3-port branch includes my PR #54 that fixed a bunch of compatibility issues. I've been using that branch on python 3.6 and 3.7 with no issues. It would be good to ship that to pypi, but it's usable as-is: https://github.com/azoner/pyx12/tree/py3-port |
@lucaswiman is there a way to do pip install for this python 3? Or do you copy over the source code and use it with python 3? |
I tried using this module with Python3. Are there any plans to make it compatible with Python3?
The text was updated successfully, but these errors were encountered: