On Monday, July 28, 2003, at 11:28 PM, Christopher Armstrong wrote:
I dread the day that parts of Twisted start making it into Python core.
Why? The core reactor is pretty stable, pretty small, and now people who have expressed distress at the state of other portions of Twisted want to use it.
If it ever does, though, I want to "brute-force" the versioning issue and put it in a top-level package with a name other than "twisted"
Agreed.
(And I'm sure Guido would agree, as he doesn't like names like "twisted" and "optik").
Maybe we can call it 'reactor.*'? (Or, for all you Sw. Eng. fans out there, "patterns.reactor.*" :-))
That way if we continue to develop bits that are also in Python, there will be no versioning clashes. We've all seen this issue with the (*flinch* *flinch*) `xml' package.
Yes, please, let's let application authors choose WHICH version of this they want to run with; ostensibly the core Python version would be much more stable, and upgrades to it could happen with excruciating attention to backwards compat.