Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Should models be bundled? #29

Open
theju opened this issue Mar 27, 2012 · 2 comments
Open

Should models be bundled? #29

theju opened this issue Mar 27, 2012 · 2 comments
Assignees
@tuxcanfly
Milestone
1.0 - Initial Maj...

Comments

@theju
Copy link
Contributor

theju commented Mar 27, 2012

Lots of the gateways have either redundant columns or make frequent changes in the columns their datatype etc. Should we be bundling models or leave it to the user to decide to pick the columns of his/her choice?
@theju theju mentioned this issue Apr 20, 2012
Closed
@theju
Copy link
Contributor Author

theju commented Apr 20, 2012

My personal opinion is to provide these separately and I have an itch to deprecate this in v0.05.

This change will affect:

  • authorize.net
  • amazon fps
  • eway
  • google checkout
  • world pay

@tuxcanfly
Copy link
Member

Since we're working on de-integrating django in #71 , this would be a good time to decide either to move these models to the django plugins or remove them altogether.

@ghost ghost assigned tuxcanfly May 14, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tuxcanfly tuxcanfly

Labels
None yet
Projects
None yet
Milestone
1.0 - Initial Major Release
Development

No branches or pull requests
2 participants
@theju @tuxcanfly