floguy - Project Hosting on Google Code

User Profile		Updates

Older Jun 21, 2009 django-pagination issue 50 (TemplateSyntaxError) Status changed - This only happens if you put the {% load pagination_tags %} in a different template block scope than the {% paginate %} tag, which is inherent to Django, not just to django- pagination. There's really nothing I can do about this. Thanks for taking the time to file a bug report, though! Status: WontFix This only happens if you put the {% load pagination_tags %} in a different template block scope than the {% paginate %} tag, which is inherent to Django, not just to django- pagination. There's really nothing I can do about this. Thanks for taking the time to file a bug report, though! Status: WontFix May 22, 2009 pytyrant issue 5 (Haven't support table database (tct) ?) commented on - Last night I decided to do a bit of hacking to add an abstraction over the table type. It's early days, it's unofficial, and there's no docs as of yet, but if you're interested in my progress you can check it out here: http://github.com/ericflo/pytyrant/tree/master Look for PyTableTyrant in pytyrant.py Last night I decided to do a bit of hacking to add an abstraction over the table type. It's early days, it's unofficial, and there's no docs as of yet, but if you're interested in my progress you can check it out here: http://github.com/ericflo/pytyrant/tree/master Look for PyTableTyrant in pytyrant.py May 21, 2009 pytyrant issue 6 (Stupid amount of concurrent connections starts throwing erro...) commented on - I've gone ahead and opened a ticket in the django-tokyo-sessions ticket tracker. As the author of django-tokyo-sessions, I can tell you that it's still an early project, and I wouldn't be surprised if there were a bug somewhere in there where it wasn't closing connections properly. Here's a link to the ticket: http://github.com/ericflo/django-tokyo-sessions/issues/#issue/1 I've gone ahead and opened a ticket in the django-tokyo-sessions ticket tracker. As the author of django-tokyo-sessions, I can tell you that it's still an early project, and I wouldn't be surprised if there were a bug somewhere in there where it wasn't closing connections properly. Here's a link to the ticket: http://github.com/ericflo/django-tokyo-sessions/issues/#issue/1 Mar 31, 2009 django-threa...comments django-threadedcomments-0.5.1.tar.gz (Release 0.5.1) file uploaded - Labels: Featured Labels: Featured Mar 31, 2009 django-threa...comments threadedcomments-0.5.tar.gz (Release 0.5) file uploaded - Labels: Featured Labels: Featured Mar 30, 2009 django-hotclub PyCon2009SprintIdeas Wiki page edited Mar 30, 2009 django-hotclub PyCon2009SprintIdeas Wiki page edited Mar 30, 2009 django-hotclub PyCon2009SprintIdeas Wiki page edited Mar 29, 2009 django-pagination r50 (Nitpicks.) committed - Nitpicks. Nitpicks. Mar 29, 2009 django-pagination r49 (Fixed a problem where the middleware accessed POST on every ...) committed - Fixed a problem where the middleware accessed POST on every request, freezing upload_handlers at that point. Fixed a problem where the middleware accessed POST on every request, freezing upload_handlers at that point. Mar 29, 2009 django-pagination r48 (Nitpicky stuff and PEP8ification) committed - Nitpicky stuff and PEP8ification Nitpicky stuff and PEP8ification Mar 29, 2009 django-pagination r47 (Merge branch 'master' of git@github.com:ericflo/django-pagin...) committed - Merge branch 'master' of git@github.com:ericflo/django-pagination Merge branch 'master' of git@github.com:ericflo/django-pagination Feb 04, 2009 django-pagination issue 39 (autopaginate tag makes queryset not lazy with django.views.g...) Status changed - I cannot reproduce this issue. I suspect you're doing {% if posts_list %} or something similar before calling autopaginate. Also, you shouldn't have to use autopaginate in conjunction with generic views. Generic views do the pagination for you already, so you should only have to call the paginate tag. Status: Invalid I cannot reproduce this issue. I suspect you're doing {% if posts_list %} or something similar before calling autopaginate. Also, you shouldn't have to use autopaginate in conjunction with generic views. Generic views do the pagination for you already, so you should only have to call the paginate tag. Status: Invalid Jan 24, 2009 django-hotclub SprintIdeas (What should you work on?) Wiki page edited Jan 24, 2009 django-hotclub SprintResults (what we've achieved in this sprint) Wiki page edited Jan 24, 2009 django-oembed r29 (Added a setup.py to django-oembed) committed - Added a setup.py to django-oembed Added a setup.py to django-oembed Jan 20, 2009 django-hotclub SprintIdeas (What should you work on?) Wiki page edited Jan 15, 2009 django-things r47 (Fixed a bug that cropped up due to the latest version of Dja...) committed - Fixed a bug that cropped up due to the latest version of Django. Thanks, Mitch Chapman! Fixed a bug that cropped up due to the latest version of Django. Thanks, Mitch Chapman! Jan 14, 2009 django-hotclub issue 146 ('things' in Pinax 0.5.1 breaks with recent django trunk (r97...) changed - Status: Accepted Owner: floguy Status: Accepted Owner: floguy Dec 14, 2008 django-oembed r28 (Merged the updates from idangazit. Thank you!) committed - Merged the updates from idangazit. Thank you! Merged the updates from idangazit. Thank you! Dec 07, 2008 django-pagination r46 (Added Portuguese translation) committed - Added Portuguese translation Added Portuguese translation Dec 06, 2008 django-avatar issue 6 (PNG file upload causes IOError) commented on - rushabd: This is apparently a limitation of PIL itself. rushabd: This is apparently a limitation of PIL itself. Dec 04, 2008 django-pagination django-pagination-1.0.5.tar.gz (django-pagination-1.0.5.tar.gz) file uploaded - Labels: Featured Labels: Featured Dec 04, 2008 django-pagination issue 28 (django-pagination causes 500 error on invalid page) Status changed - Fixed in r45 Status: Fixed Fixed in r45 Status: Fixed Dec 04, 2008 django-pagination r45 (Fixed #28. Added the ability for the autopaginate tag to ra...) committed - Fixed #28. Added the ability for the autopaginate tag to raise an Http404. Also documented that feature as well as the other settings. Fixed #28. Added the ability for the autopaginate tag to raise an Http404. Also documented that feature as well as the other settings. Dec 04, 2008 django-avatar django-avatar-1.0.1.tar.gz (django-avatar-1.0.1.tar.gz) file uploaded - Labels: Featured Labels: Featured Dec 04, 2008 django-avatar issue 7 (Avatar / Pictures not deleted from file system) Status changed - Agreed, but it's a little bit tricky. Since we generate more pictures than there are database entries (for speed), we have no reference to those except when they are attempted to be accessed the next time. I guess a sane default would be to delete all of the predetermined sizes. Status: Accepted Agreed, but it's a little bit tricky. Since we generate more pictures than there are database entries (for speed), we have no reference to those except when they are attempted to be accessed the next time. I guess a sane default would be to delete all of the predetermined sizes. Status: Accepted Dec 04, 2008 django-avatar issue 6 (PNG file upload causes IOError) Status changed - Fixed in r35 Status: Fixed Fixed in r35 Status: Fixed Dec 04, 2008 django-avatar issue 5 (PNG file upload causes typeerror) Status changed - Fixed in r35 Status: Fixed Fixed in r35 Status: Fixed Dec 04, 2008 django-avatar r35 (Fixed the apparent problem with PNG and S3 that some were se...) committed - Fixed the apparent problem with PNG and S3 that some were seeing. Thanks, msaelices and bryanveloso. Along with that fix also comes support for not resizing an image if it's already the correct size. Fixed the apparent problem with PNG and S3 that some were seeing. Thanks, msaelices and bryanveloso. Along with that fix also comes support for not resizing an image if it's already the correct size. Dec 01, 2008 django-hotclub issue 108 (Project slugs with underscores and hyphens fails) Status changed - Whoops, I fixed this bug before knowing about this ticket. Status: Fixed Whoops, I fixed this bug before knowing about this ticket. Status: Fixed Nov 28, 2008 django-pagination issue 28 (django-pagination causes 500 error on invalid page) Status changed - Status: Accepted Status: Accepted Nov 28, 2008 django-pagination issue 29 (Google's App Engine Django Template project) Status changed - I'm not committed to supporting Google App Engine. If someone were to provide a patch, I'd happily do it though :) Status: WontFix I'm not committed to supporting Google App Engine. If someone were to provide a patch, I'd happily do it though :) Status: WontFix Nov 28, 2008 django-pagination issue 30 ("Show X records" <select> feature?) Status changed - Yes, that's the correct syntax. Status: Invalid Yes, that's the correct syntax. Status: Invalid Nov 28, 2008 django-pagination issue 31 (diffrent blocks == error) Status changed - This is a property of Django itself...there's nothing I can do about this in the context of a Django project. Status: WontFix This is a property of Django itself...there's nothing I can do about this in the context of a Django project. Status: WontFix Nov 28, 2008 django-voting issue 12 (Add date_submitted field on votes.) commented on - aron: No, auto_now is generally considered bad practice. The only reason it is still in Django is due to an oversight in the release 1.0. It should have been removed. So, while it's still "supported" it's not a good idea to use it because it's going to be one of the first things to go once backwards incompatible changes start happening again in a few years. aron: No, auto_now is generally considered bad practice. The only reason it is still in Django is due to an oversight in the release 1.0. It should have been removed. So, while it's still "supported" it's not a good idea to use it because it's going to be one of the first things to go once backwards incompatible changes start happening again in a few years. Nov 28, 2008 django-locations r16 (Made the global api key cache work correctly.) committed - Made the global api key cache work correctly. Made the global api key cache work correctly. Nov 28, 2008 django-locations r15 (Fixed a bug where lazy_key wasn't being called.) committed - Fixed a bug where lazy_key wasn't being called. Fixed a bug where lazy_key wasn't being called. Nov 28, 2008 django-locations r14 (Fixed a localization and message creation bug.) committed - Fixed a localization and message creation bug. Fixed a localization and message creation bug. Nov 28, 2008 django-locations r13 (Whoops, made a Pinax-specific reference. Removing that refe...) committed - Whoops, made a Pinax-specific reference. Removing that reference. Whoops, made a Pinax-specific reference. Removing that reference. Nov 28, 2008 django-locations r12 (Made the setting fetching lazy so that all other apps run ev...) committed - Made the setting fetching lazy so that all other apps run even when no key is installed, but the error is still raised when django-locations views are called. Made the setting fetching lazy so that all other apps run even when no key is installed, but the error is still raised when django-locations views are called. Nov 28, 2008 django-locations r11 (Factor out the setting fetching and raise a helpful error me...) committed - Factor out the setting fetching and raise a helpful error message if an API key is not found. Factor out the setting fetching and raise a helpful error message if an API key is not found. Nov 28, 2008 django-locations r10 (Cleanup and mostly stylistic changes in preparation for incl...) committed - Cleanup and mostly stylistic changes in preparation for inclusion in the Pinax project. Cleanup and mostly stylistic changes in preparation for inclusion in the Pinax project. Nov 24, 2008 django-hotclub issue 116 (better verbiage needed for 0 search results) Status changed - Fixed in r1227 Status: Fixed Fixed in r1227 Status: Fixed Nov 24, 2008 django-hotclub issue 123 (contradictory avatar wording) Status changed - Fixed in r1226 Status: Fixed Fixed in r1226 Status: Fixed Nov 24, 2008 django-hotclub issue 123 (contradictory avatar wording) changed - Status: Started Owner: floguy Status: Started Owner: floguy Nov 24, 2008 django-hotclub issue 124 (Preventing a user from registering based upon a banned IP li...) reported - There are always going to be bad apples, but we can't let them spoil the bunch! Once we have determined that someone is malicious or otherwise bad for the community, we should be able to ban them and prevent them from re-registering based upon their IP address. There are always going to be bad apples, but we can't let them spoil the bunch! Once we have determined that someone is malicious or otherwise bad for the community, we should be able to ban them and prevent them from re-registering based upon their IP address. Nov 08, 2008 django-threa...comments r126 (Fixed some relative import problems.) committed - Fixed some relative import problems. Fixed some relative import problems. Nov 07, 2008 django-pagination issue 28 (django-pagination causes 500 error on invalid page) commented on - Agreed, I think the solution is to insert an invalid_page value or something into the context, so that it's up to the template author to gracefully handle that and not attempt to use pagination if there is an invalid_page == True. Of course the default template will handle it correctly as well. Agreed, I think the solution is to insert an invalid_page value or something into the context, so that it's up to the template author to gracefully handle that and not attempt to use pagination if there is an invalid_page == True. Of course the default template will handle it correctly as well.

issue 6 (Stupid amount of concurrent connections starts throwing erro...) commented on - I've gone ahead and opened a ticket in the django-tokyo-sessions ticket tracker. As the author of django-tokyo-sessions, I can tell you that it's still an early project, and I wouldn't be surprised if there were a bug somewhere in there where it wasn't closing connections properly. Here's a link to the ticket: http://github.com/ericflo/django-tokyo-sessions/issues/#issue/1

I've gone ahead and opened a ticket in the django-tokyo-sessions ticket tracker. As the author of django-tokyo-sessions, I can tell you that it's still an early project, and I wouldn't be surprised if there were a bug somewhere in there where it wasn't closing connections properly. Here's a link to the ticket: http://github.com/ericflo/django-tokyo-sessions/issues/#issue/1

Older