Revision history [back]
Markdown2 is somebody else's module, so there is no guarantee that the changes will be merged into the main project - it is up to the person who is in charge.
As of now (June 2011) - a development version of django-avatar is required. Is that a problem for the Linux packaging?
Django-followit will be released on pypi and it will be maintained on github, maybe other modules will be split off in the same fashion, in fact it can be done now.
Markdown2 is are somebody else's module, so there is no guarantee that the changes will be merged into the respective main project projects - it is up to the person people who is are in charge.
As of now (June 2011) - a development version of django-avatar is required. Is that a problem for the Linux packaging?
Django-followit will be released on pypi and it will be maintained on github, maybe other modules will be split off in the same fashion, in fact it can be done now.
Markdown2 Warkdown2 are somebody else's module, so there is no guarantee that the changes will be merged into the respective main projects - it is up to the people who are in charge.
As of now (June 2011) - a development version of django-avatar is required. Is that a problem for the Linux packaging?
Django-followit will be released on pypi and it will be maintained on github, maybe other modules will be split off in the same fashion, in fact it can be done now.
Warkdown2 Django-avatar and markdown2 are somebody else's module, modules, so there is no guarantee that the changes will be merged into the respective main projects - it is up to the people who are in charge.
As of now (June 2011) - a development version of django-avatar is required. Is that a problem for the Linux packaging?
Django-followit will be released on pypi and it will be maintained on github, maybe other modules will be split off in the same fashion, in fact it can be done now.