"The link I posted above still seems to be valid. At least it still contains a link to some kind of unsubscribe page. If this doesn't work for you, I guess, you could try their forums."
- Horst Gutmann
"Then I'd suggest you ask on drupal.org :-) Since this post is by now more than 5 years old and I've dropped Drupal quite a while ago, the fine folks over there will definitely be more able to help you than I ;-)"
- Horst Gutmann
"Then I'd suggest you ask on drupal.org :-) Since this post is by now more than 5 years old and I've dropped Drupal quite a while ago, the fine folks over there will definitely be more able to help you than I ;-)"
- Horst Gutmann
"Mostly because I've used virtualenv + pip for a long time for trying out small stuff. If all you want is to write a simple script that requires a handful of dependencies, writing a buildout.cfg and a setup.py always felt like total overhead to me. Sure, the moment I need other dependencies and also want to easily redistribute the result, buildout is still an option, but somehow that moment hasn't come in a really long time for me :-) And *if* there is some work to do besides the actual Python dependency management I usually just put it into a fabfile since I use Fabric anyway for deploying sites :-)"
- Horst Gutmann
"Mostly because I've used virtualenv + pip for a long time for trying out small stuff. If all you want is to write a simple script that requires a handful of dependencies, writing a buildout.cfg and a setup.py always felt like total overhead to me. Sure, the moment I need other dependencies and also want to easily redistribute the result, buildout is still an option, but somehow that moment hasn't come in a really long time for me :-) And *if* there is some work to do besides the actual Python dependency management I usually just put it into a fabfile since I use Fabric anyway for deploying sites :-)"
- Horst Gutmann
"No, not really, sorry. But judging by the age of this package and the lack of activity in the issue tracker I think this kind of looks abandoned."
- Horst Gutmann
"No, not really, sorry. But judging by the age of this package and the lack of activity in the issue tracker I think this kind of looks abandoned."
- Horst Gutmann
zerok on Version 0.7 Codename "Grappa" of Flask, the microframework for Python based on Werkzeug, Jinja 2 and good intentions is released - http://www.reddit.com/r...
"I haven't really used Bottle so far but just by looking a little bit through the docs I personally prefer Flask simple on the API level. Feature-wise they seem to be more or less on the same level, but I really like Flask's approach of handling slightly larger apps with modules/blueprints. But ignoring that for a second, as far as I can tell Flask also has a lot more documentation which should make it far easier for you."
- Horst Gutmann
"Ich werde ohnehin mal versuchen, einen "normalen" Photowalk in Graz zu organisieren. Dann hast ja wieder eine Chance ;-) Und garantiert nicht am Muttertag!"
- Horst Gutmann
"Ich werde ohnehin mal versuchen, einen "normalen" Photowalk in Graz zu organisieren. Dann hast ja wieder eine Chance ;-) Und garantiert nicht am Muttertag!"
- Horst Gutmann
"Hi :-) The whole migration topic becomes even more complicated when you take app authors into account that want to provide a simple update path if the db schema changes on their end. For instance I'm currently thinking about integrating a patch into django-flatblocks that would change the database structure slightly. To make the update as painless as possible for users I'd love to also migrate to South while I'm at it. This would at least only involve doing one fake migration on each installation. But then we might end up with clashes once you as a user also add your own migrations. So far I can only imagine that this might work with some kind of weird versioning scheme for the migration files ... I guess I should look for some headache-pills ;-)"
- Horst Gutmann
"Hi :-) The whole migration topic becomes even more complicated when you take app authors into account that want to provide a simple update path if the db schema changes on their end. For instance I'm currently thinking about integrating a patch into django-flatblocks that would change the database structure slightly. To make the update as painless as possible for users I'd love to also migrate to South while I'm at it. This would at least only involve doing one fake migration on each installation. But then we might end up with clashes once you as a user also add your own migrations. So far I can only imagine that this might work with some kind of weird versioning scheme for the migration files ... I guess I should look for some headache-pills ;-)"
- Horst Gutmann
"The idea is definitely a nice one, but - as you've already written - the implementation style is weird, to say the least. -p for *not* pushing, no duplicate content check, an __init__ method that actually does the whole execution ... I'm also not really onboard with the used data structure, but it guess it has a point if grep is the primary interface. A nice idea and an implementation that hopefully improves over time :-)"
- Horst Gutmann
"The idea is definitely a nice one, but - as you've already written - the implementation style is weird, to say the least. -p for *not* pushing, no duplicate content check, an __init__ method that actually does the whole execution ... I'm also not really onboard with the used data structure, but it guess it has a point if grep is the primary interface. A nice idea and an implementation that hopefully improves over time :-)"
- Horst Gutmann
"I absolutely agree with your point about microblogging. IMO it works really nice if you want to announce something or for short comments, but most of the time I want to write just a little more to add some substance to something I wanted to say. Regarding file based blog systems like Jekyll and Blogofile: I made that switch about a year ago but sadly couldn't find anything that matched the way I'd have liked to organize my files, so I had to write a custom solution (which I ditched and rewrote just 2 weeks ago again :-P). I just don't like the idea of not giving each post its own folder and therefor being forced to put metadata in the same file as the actual content. It also kind of makes adding files to a specific post kind of messy IMO. Regarding the rebuild-issue you've mentioned: Especially with (as you've mentioned) posts going back 8 years (which in my case means about 1200 posts) was definitely a show-stopper. I haven't really come up with a clean solution for this that also..."
- Horst Gutmann
"I absolutely agree with your point about microblogging. IMO it works really nice if you want to announce something or for short comments, but most of the time I want to write just a little more to add some substance to something I wanted to say. Regarding file based blog systems like Jekyll and Blogofile: I made that switch about a year ago but sadly couldn't find anything that matched the way I'd have liked to organize my files, so I had to write a custom solution (which I ditched and rewrote just 2 weeks ago again :-P). I just don't like the idea of not giving each post its own folder and therefor being forced to put metadata in the same file as the actual content. It also kind of makes adding files to a specific post kind of messy IMO. Regarding the rebuild-issue you've mentioned: Especially with (as you've mentioned) posts going back 8 years (which in my case means about 1200 posts) was definitely a show-stopper. I haven't really come up with a clean solution for this that also..."
- Horst Gutmann
"I absolutely agree with your point about microblogging. IMO it works really nice if you want to announce something or for short comments, but most of the time I want to write just a little more to add some substance to something I wanted to say. Regarding file based blog systems like Jekyll and Blogofile: I made that switch about a year ago but sadly couldn't find anything that matched the way I'd have liked to organize my files, so I had to write a custom solution (which I ditched and rewrote just 2 weeks ago again :-P). I just don't like the idea of not giving each post its own folder and therefor being forced to put metadata in the same file as the actual content. It also kind of makes adding files to a specific post kind of messy IMO. Regarding the rebuild-issue you've mentioned: Especially with (as you've mentioned) posts going back 8 years (which in my case means about 1200 posts) was definitely a show-stopper. I haven't really come up with a clean solution for this that also..."
- Horst Gutmann