3 ms·
Do you have good tests? I've done this pretty recently and it got somewhat messy -- though I had great test coverage on the project that I upgraded, so it proba
by jsdalton 13y ago
Do you have good tests? I've done this pretty recently and it got somewhat messy -- though I had great test coverage on the project that I upgraded, so it probably only took a day or so.
The main road bump I hit was Django Piston. It's totally broken past 1.5 and there are a gazillion forks that solved non-overlapping subsets of the problems I was having.
- Demiurge 13y agoMakes me pat myself on the back for trying to resist non-essential packages if I can roll my own, as much as possible :)
- raverbashing 13y agoYes Some people will try to solve whatever problem they have by searching for a package. Even if this could be solved with a couple of lines of code Yes, reinventing is bad. Yes, good libraries have been tested, are supported through upgrades, etc. But I'm very wary of libraries. Beyond the learning curve, then finding out it doesn't solve your problem or it has some stupid bugs, I think it's usually easier to roll your own except for the most mainstream libraries.
- Daishiman 13y agoYes, Piston is an absolute PITA. However, Class-Based Views nowadays solve the same problem domain much better, and I would think that it's easier to write a CBV that's support some of Piston's idioms and refactor a bit than try to take Piston the latest Django version.