Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #25759
| References | <5009F0D9.1050900@stoneleaf.us> <500A2260.20806@fossworkflowguides.com> <500A61FB.7060600@stoneleaf.us> <CAPTjJmqST800FoLwSX=kqFBf0WYyAUvWJ6Xot2FCsYSnEufdUg@mail.gmail.com> <500AF1AD.5080106@stoneleaf.us> |
|---|---|
| Date | 2012-07-22 04:28 +1000 |
| Subject | Re: ANN: dbf.py 0.94 |
| From | Chris Angelico <rosuav@gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.2393.1342895319.4697.python-list@python.org> (permalink) |
On Sun, Jul 22, 2012 at 4:15 AM, Ethan Furman <ethan@stoneleaf.us> wrote: > I'll support 3.3+, but not with the same code base: I want to use all the > cool features that 3.3 has! :) The trouble with double-codebasing is that you have double maintenance. But sure. So long as your time isn't under great pressure, it can be quite effective. Recommendation: Figure out a way to minimize double-handling of things. One way might be to have source control manage it for you - apply a patch to your 3.3+ source tree, then merge it into your 2.4+ tree and see if it applies cleanly. I dunno how successful that'd be, but I really dread the idea of maintaining, unassisted, two identical projects in two dialects of the same language. Recipe for burnout I'd predict. ChrisA
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: ANN: dbf.py 0.94 Chris Angelico <rosuav@gmail.com> - 2012-07-22 04:28 +1000
csiph-web