brosner - Project Hosting on Google Code

User Profile		Updates

Today 21 hours ago django-tagging issue 231 (How to get tags fields without parse and hit the database ge...) changed - Duplicate of #235 — using that ticket as it has a patch. Status: Duplicate Duplicate of #235 — using that ticket as it has a patch. Status: Duplicate 21 hours ago django-tagging issue 235 (TagField causes DB hit for every tagged object loaded) commented on - Issue 231 has been merged into this issue. Issue 231 has been merged into this issue. 21 hours ago django-tagging issue 222 (Presence of TagField on a model generates a SQL per object i...) Status changed - Duplicate of #235 — using that ticket as it has a patch. Status: Duplicate Duplicate of #235 — using that ticket as it has a patch. Status: Duplicate 21 hours ago django-tagging issue 235 (TagField causes DB hit for every tagged object loaded) Status changed - Status: Accepted Status: Accepted 21 hours ago django-tagging issue 234 (django-tagging incompatible with django 1.2) Status changed - Status: Duplicate Status: Duplicate 21 hours ago django-tagging issue 233 (Django Tagging fails in the last pre-alpha release of Django) Status changed - Status: Accepted Status: Accepted 21 hours ago django-tagging issue 233 (Django Tagging fails in the last pre-alpha release of Django) commented on - I haven't looked too deeply into this issue, but the latest patch works on only Django 1.2. I suspect this will fail on 1.0 and 1.1. 1.0 is less important as I'm okay making the next release 1.1 the minimum requirement. I haven't looked too deeply into this issue, but the latest patch works on only Django 1.2. I suspect this will fail on 1.0 and 1.1. 1.0 is less important as I'm okay making the next release 1.1 the minimum requirement. Older Nov 05, 2009 django-tagging issue 28 (TagField doesn't sync the list when you TagField doesn't syn...) Status changed - Status: Fixed Status: Fixed Nov 05, 2009 django-tagging issue 28 (TagField doesn't sync the list when you TagField doesn't syn...) Summary changed - Fixed in r170. Summary: TagField doesn't sync the list when you TagField doesn't sync when removing tags Fixed in r170. Summary: TagField doesn't sync the list when you TagField doesn't sync when removing tags Nov 05, 2009 django-tagging r171 ([0.3.X] Fixed issue #28 — properly update TagField tag insta...) committed - [0.3.X] Fixed issue #28 — properly update TagField tag instance cache when loading the object to keep everything in sync. Thanks ebartels and carljm for the legwork. Backport of r170 from trunk [0.3.X] Fixed issue #28 — properly update TagField tag instance cache when loading the object to keep everything in sync. Thanks ebartels and carljm for the legwork. Backport of r170 from trunk Nov 05, 2009 django-tagging r170 (Fixed issue #28 — properly update TagField tag instance cach...) committed - Fixed issue #28 — properly update TagField tag instance cache when loading the object to keep everything in sync. Thanks ebartels and carljm for the legwork. Fixed issue #28 — properly update TagField tag instance cache when loading the object to keep everything in sync. Thanks ebartels and carljm for the legwork. Nov 03, 2009 django-tagging issue 220 (The testsuite fails if run with python 2.6) Status changed - Fixed in r168. Status: Fixed Fixed in r168. Status: Fixed Nov 03, 2009 django-tagging r169 ([0.3.X] Fixed issue #220 — coerce Exception object using str...) committed - [0.3.X] Fixed issue #220 — coerce Exception object using str for consistency on 2.5 and 2.6. Thanks phxx.de for the report. Backport of r168 from trunk [0.3.X] Fixed issue #220 — coerce Exception object using str for consistency on 2.5 and 2.6. Thanks phxx.de for the report. Backport of r168 from trunk Nov 03, 2009 django-tagging r168 (Fixed issue #220 — coerce Exception object using str for con...) committed - Fixed issue #220 — coerce Exception object using str for consistency on 2.5 and 2.6. Thanks phxx.de for the report. Fixed issue #220 — coerce Exception object using str for consistency on 2.5 and 2.6. Thanks phxx.de for the report. Nov 03, 2009 django-tagging issue 220 (The testsuite fails if run with python 2.6) Status changed - Status: Accepted Status: Accepted Oct 14, 2009 django-photologue issue 127 (Unusual Filenames Error) commented on - I can't test right now, but could you do us a favor and provide the error you are getting and how you were able to reproduce. At the time of fix this was working correctly. I won't put it pass me for making a mistake ;-) I can't test right now, but could you do us a favor and provide the error you are getting and how you were able to reproduce. At the time of fix this was working correctly. I won't put it pass me for making a mistake ;-) Aug 25, 2009 django-voting issue 18 (ctype assigned twice in get_scores_in_bulk()) Status changed - Fixed in r73 Status: Fixed Fixed in r73 Status: Fixed Aug 25, 2009 django-voting r73 (fixed issue #18 — removed a duplicate line) committed - fixed issue #18 — removed a duplicate line fixed issue #18 — removed a duplicate line Aug 25, 2009 django-voting issue 26 (duplicate line) Status changed - Duplicate of #18 Status: Duplicate Duplicate of #18 Status: Duplicate Aug 25, 2009 django-voting r72 (version bump) committed - version bump version bump Aug 25, 2009 django-voting issue 25 (Patch to work with pinax-devel 0.7.2beta) Status changed - Duplicate of issue #24 Status: Duplicate Duplicate of issue #24 Status: Duplicate Aug 25, 2009 django-voting issue 24 (get_scores_in_bulk() broken with django svn (1.1)) Status changed - Fixed in r70. Status: Fixed Fixed in r70. Status: Fixed Aug 25, 2009 django-voting r71 (modified distribution to follow Django convention (and likel...) committed - modified distribution to follow Django convention (and likely available) modified distribution to follow Django convention (and likely available) Aug 25, 2009 django-voting r70 (Fixed #24 — corrects get_scores_in_bulk to work on both 1.0 ...) committed - Fixed #24 — corrects get_scores_in_bulk to work on both 1.0 and 1.1 This patch is based on the work from jsmullyan (thanks!) and improves it slightly to match the 1.0 SQL. Fixed #24 — corrects get_scores_in_bulk to work on both 1.0 and 1.1 This patch is based on the work from jsmullyan (thanks!) and improves it slightly to match the 1.0 SQL. Aug 23, 2009 django-tagging issue 175 (Unable to run tests.py due to "DJANGO_SETTINGS_MODULE is und...) commented on - There is a tool. It comes with Django too ;-) django-admin.py test --settings=tagging.tests.settings There is a tool. It comes with Django too ;-) django-admin.py test --settings=tagging.tests.settings Aug 22, 2009 django-tagging r167 ([0.3.X] Fixed issue #212 — convert docstrings to proper unit...) committed - [0.3.X] Fixed issue #212 — convert docstrings to proper unittests Huge thanks to anball for providing a working patch Backport of r166 from trunk [0.3.X] Fixed issue #212 — convert docstrings to proper unittests Huge thanks to anball for providing a working patch Backport of r166 from trunk Aug 22, 2009 django-tagging issue 212 (the unit tests in tagging/tests/tests.py are an amorphous bl...) Status changed - Fixed in r166 — thanks! Status: Fixed Fixed in r166 — thanks! Status: Fixed Aug 22, 2009 django-tagging r166 (Fixed issue #212 — convert docstrings to proper unittests H...) committed - Fixed issue #212 — convert docstrings to proper unittests Huge thanks to anball for providing a working patch Fixed issue #212 — convert docstrings to proper unittests Huge thanks to anball for providing a working patch Aug 22, 2009 django-tagging issue 205 (problem running manage.py syncdb) Status changed - I suspect something wonky is going in your setup. Start fresh and try using 0.3. Report a new issue if you experience issues. Status: Invalid I suspect something wonky is going in your setup. Start fresh and try using 0.3. Report a new issue if you experience issues. Status: Invalid Aug 22, 2009 django-tagging issue 124 (Installation error on Django .96) Status changed - Django 0.96 is no longer supported. Status: Invalid Django 0.96 is no longer supported. Status: Invalid Aug 22, 2009 django-tagging issue 169 (sql error) Status changed - Status: Invalid Status: Invalid Aug 22, 2009 django-tagging issue 175 (Unable to run tests.py due to "DJANGO_SETTINGS_MODULE is und...) Status changed - This isn't how you run the tests. Make sure you are running in an environment that sets DJANGO_SETTINGS_MODULE correctly. Status: Invalid This isn't how you run the tests. Make sure you are running in an environment that sets DJANGO_SETTINGS_MODULE correctly. Status: Invalid Aug 22, 2009 django-tagging issue 195 (installation error) Status changed - This should no longer be the case. Report new issues if you are having them. Status: Fixed This should no longer be the case. Report new issues if you are having them. Status: Fixed Aug 22, 2009 django-tagging r165 (bump version in __init__.py) committed - bump version in __init__.py bump version in __init__.py Aug 22, 2009 django-tagging issue 110 (installation issue) Status changed - This shouldn't be a problem anymore since setup.py doesn't import from version from tagging/__init__.py any longer. Report new issues as they come up. Status: Fixed This shouldn't be a problem anymore since setup.py doesn't import from version from tagging/__init__.py any longer. Report new issues as they come up. Status: Fixed Aug 22, 2009 django-tagging issue 113 (install error) Status changed - This isn't an issue with django-tagging. Make sure you read the installation directions. Open new issues reporting new problems. Status: Invalid This isn't an issue with django-tagging. Make sure you read the installation directions. Open new issues reporting new problems. Status: Invalid Aug 22, 2009 django-tagging issue 159 (Not support Django 1.0) Status changed - Status: Fixed Status: Fixed Aug 22, 2009 django-tagging issue 159 (Not support Django 1.0) commented on - 0.3 is out now. 0.3 is out now. Aug 22, 2009 django-tagging issue 174 (cannot import name parse_lookup) Status changed - This is no longer an issue with 0.3. Use that over trunk in most cases (unless you are following along with development). I recommend using something like pip or easy_install to install django-tagging. You can use -U to get better upgrades (but still not perfect). Status: Fixed This is no longer an issue with 0.3. Use that over trunk in most cases (unless you are following along with development). I recommend using something like pip or easy_install to install django-tagging. You can use -U to get better upgrades (but still not perfect). Status: Fixed Aug 22, 2009 django-tagging r164 ([0.3.X] modified CHANGELOG.txt to reflect current state) committed - [0.3.X] modified CHANGELOG.txt to reflect current state [0.3.X] modified CHANGELOG.txt to reflect current state Aug 22, 2009 django-tagging r163 (modified CHANGELOG.txt to reflect current state) committed - modified CHANGELOG.txt to reflect current state modified CHANGELOG.txt to reflect current state Aug 22, 2009 django-tagging r162 ([0.3.X] modified test settings for flexibility on testing ag...) committed - [0.3.X] modified test settings for flexibility on testing against multiple databases Backport of r161 from trunk [0.3.X] modified test settings for flexibility on testing against multiple databases Backport of r161 from trunk Aug 22, 2009 django-tagging r161 (modified test settings for flexibility on testing against mu...) committed - modified test settings for flexibility on testing against multiple databases modified test settings for flexibility on testing against multiple databases Aug 22, 2009 django-tagging issue 88 (NewForms-Admin compatible admin module) Status changed - Status: Fixed Status: Fixed Aug 22, 2009 django-tagging issue 206 (error: /usr/local/lib/python2.6/dist-packages/tagging-0.2.1....) commented on - Sigh. Should have read "This isn't an issue in django-tagging." ;-) Sigh. Should have read "This isn't an issue in django-tagging." ;-) Aug 22, 2009 django-tagging issue 206 (error: /usr/local/lib/python2.6/dist-packages/tagging-0.2.1....) Status changed - This is an issue in django-tagging. Also, please use the newly released 0.3 on Django 1.0+. Status: Invalid This is an issue in django-tagging. Also, please use the newly released 0.3 on Django 1.0+. Status: Invalid Aug 22, 2009 django-tagging r160 (Create branch 0.3.X) committed - Create branch 0.3.X Create branch 0.3.X Aug 22, 2009 django-tagging issue 208 (Reporting a bug requires a google account) Status changed - Most hosted solutions are going to require users to have an account to report issues. The only other alternative is to move to a self-hosted platform (and even some of those do the same thing). django-tagging will be staying on Google Code for the time being. If it were to move I'm sure the new platform isn't going to allow anonymous bug reporting. (I wouldn't want that anyways). Status: Invalid Most hosted solutions are going to require users to have an account to report issues. The only other alternative is to move to a self-hosted platform (and even some of those do the same thing). django-tagging will be staying on Google Code for the time being. If it were to move I'm sure the new platform isn't going to allow anonymous bug reporting. (I wouldn't want that anyways). Status: Invalid Aug 22, 2009 django-tagging issue 203 (Enconter import Error!------cannot import name parse_lookup) Status changed - Version 0.2.1 didn't work on 1.0+. Please use the just released 0.3 version. Status: WontFix Version 0.2.1 didn't work on 1.0+. Please use the just released 0.3 version. Status: WontFix Aug 22, 2009 django-tagging r159 (bump for 0.4_pre which is now trunk) committed - bump for 0.4_pre which is now trunk bump for 0.4_pre which is now trunk

issue 208 (Reporting a bug requires a google account) Status changed - Most hosted solutions are going to require users to have an account to report issues. The only other alternative is to move to a self-hosted platform (and even some of those do the same thing). django-tagging will be staying on Google Code for the time being. If it were to move I'm sure the new platform isn't going to allow anonymous bug reporting. (I wouldn't want that anyways).

Status: Invalid

Most hosted solutions are going to require users to have an account to report issues. The only other alternative is to move to a self-hosted platform (and even some of those do the same thing). django-tagging will be staying on Google Code for the time being. If it were to move I'm sure the new platform isn't going to allow anonymous bug reporting. (I wouldn't want that anyways).

Status: Invalid

Today

Older