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.

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

Get rid of denorm (unless it gets actually released) #7

Open
mjtamlyn opened this issue Jul 16, 2012 · 5 comments
Open

Get rid of denorm (unless it gets actually released) #7

mjtamlyn opened this issue Jul 16, 2012 · 5 comments

Comments

@mjtamlyn
Copy link
Contributor

cc @jturnbull

Denorm has no release on pypi so we can't really be using it. Either we should get rid of it (preferably by getting rid of the nested-ness of the categories by default) or by adapting the code so that it doesn't use denorm any more. Perhaps look at how FeinCMS does its _cached_url property

@jturnbull
Copy link
Contributor

I'd propose two different category extensions: this, the hierarchical category setup (we should stick the latest denorm on pypi) and a new, simple flat category extension.

@mjtamlyn
Copy link
Contributor Author

+7000000

@meshy
Copy link
Contributor

meshy commented Oct 17, 2012

We could bundle denorm in the same way the packages are bundled in requests...

@meshy
Copy link
Contributor

meshy commented Sep 3, 2013

If i'm not mistaken, denorm will fail when it comes to django 1.6's new way of doing transactions. Perhaps we should get rid of it even if it ever does get on pypi.

@mjtamlyn
Copy link
Contributor Author

mjtamlyn commented Sep 3, 2013

That depends which version of denorm you're using, but yes there is an issue there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants