New version, 1.1, of the pythonic web application framework, Django, has been released.
Created attachment 199675 [details] Initial ebuild based on django 1.0.2 with some minor corrections
Created attachment 199679 [details] minor fix for typo
Please note that this has just been released within the last 24 hours. The maintainers may choose to wait a few days before including this in portage. Thanks for reporting!
Created attachment 199685 [details] fix to MY_PY that had bad ref.
Created attachment 199687 [details] final working version, hey! Builds fine with USE="bash-completion mysql sqlite vhosts doc -examples -postgres -test" on stable amd64. Docs build successfully with sphinx-0.5.2 All tests pass. I'd say this is good to go. Cheers, Your friendly neighborhood trustee. cheerio.
(In reply to comment #5) Please attach unidiff patch against 1.0.2-r1 ebuild, not including useless/incorrect changes.
np on the unidiff, but what changes where useless/incorrect? I changed MY_P, removing the "-final" business. + correct I added in the var DATABASE_NAME. noted in the django trac wiki as the correct method used to run tests. I also changed the text in ewarn to the correct version number. Finally, I removed the deprecated workaround for the tests, omitted in the 1.0.2 relaese. Did I miss something? Regards, Quantumsummers
Created attachment 199747 [details] diff of django-1.0.2-r1 & proposed new ebuild Thanks for the feedback Arfrever.
Fixed.