#7799: django.template refactoring
--------------------------------------+-------------------------------------
Reporter: emulbreh | Owner: nobody
Status: new | Milestone:
Component: Template system | Version: SVN
Resolution: | Keywords: tplrf
Stage: Unreviewed | Has_patch: 1
Needs_docs: 1 | Needs_tests: 1
Needs_better_patch: 1 |
--------------------------------------+-------------------------------------
Comment (by mtredinnick):
This looks like a very large ticket and it's probably a bit risky to have
just created it, rather than as a result of a django-dev discussion (since
people might be tempted to put design thinking into the ticket comments).
That being said, you should always feel free to work on whatever you like.
''However'' (and this is very important), if you're refactoring the
template stuff, then that is '''all''' you should be doing in this patch.
No new features! Combining large changes that are only meant to reorganise
the code (and not cause regressions) with things that change features
isn't fair to anybody and will lead to the ticket being closed as wontfix
because you aren't doing things in a way that allows us to work properly.
A number of the changes you are proposing are reasonably controversial and
bear in mind that Tom Tobin (korpios) is also working in this are on some
refactoring (which he announced on django-dev), so you should probably
check in with him, too.
So, yes, there's probably some stuff to do here, but keep things
manageable. Make it just a refactoring. Those other tickets exist to solve
their individual problems already and one issue per ticket is the
preferred way to work unless it's absolutely unavoidable (we never mind
putting certain fixes on hold until a reasonably certain refactor lands,
so that isn't an issue if the refactoring is sensible). Separate out
things that are actually problematic from things where you would just
prefer a different name -- which usually are just rearranging the
furniture rather than improvements, since everybody likes different names,
although there are exceptions of course -- and from the things that add
new functionality.
--
Ticket URL: <http://code.djangoproject.com/ticket/7799#comment:2>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
