-
Notifications
You must be signed in to change notification settings - Fork 3
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
Python/Django implementation #1
base: master
Are you sure you want to change the base?
Conversation
- `find_packages()` does not respect `package_dir` and needs to be explicitly told to search a sub directory package. - `install` and `develop` were generating the fixture in the /tmp directory, but the files were not copied to the target directory. - The `test` command on python 2 uses an 'in place' install of the package, so the build_py phase is never executed. It's necessary for the test command to manually build the fixture before execution.
This is awesome ryan! Thank you so much. I'm going to try to review this tomorrow. |
Hi - any objection to me going ahead and uploading this to pypi? |
None whatsoever! |
Also, fuck. I'm really sorry I haven't landed this already. Completely fell off the radar. |
Bump. This could be useful if merged. |
Hi @TMiguelT |
Hi, I've spent a little time working on a Django version of the models and fixtures. This also includes a simple test to ensure that the models and fixtures are compatible with Django and its test utilities. To run the test suite:
$ git checkout python $ python setup.py test
If everything looks good, what are your thoughts on releasing the package to PyPI? I'd be happy to help with/own the python releases, as well as updating the python code. It might also be worth noting that PyPI allows for multiple package owners and maintainers.