David Lyon wrote:
> So it isn't clear why you want to remove the thing that you are
> advocating works so great
Jim was quoting someone *else* that had suggested removing it (I'm not
sure how serious the original suggestion actually was though).
Cheers,
Nick.
--
Nick Coghlan | ncogh...@
On Sat, 18 Jul 2009 16:07:39 -0400, Jim Jewett
wrote:
> What about those people *without* versioning issues?
>
> I have no qualms suggesting that package management programs avoid the
> use of site-packages. Such programs do need to cater to edge cases.
I'm just wondering how that is possible?
At 04:07 PM 7/18/2009 -0400, Jim Jewett wrote:
Michael Foord wrote:
>> I agree. People with versioning issues *should* be using virtualenv.
Tarek Ziadé replied (and several people later agreed)
> Let's remove site-packages from Python then.
What about those people *without* versioning issues?
Michael Foord wrote:
>> I agree. People with versioning issues *should* be using virtualenv.
Tarek Ziadé replied (and several people later agreed)
> Let's remove site-packages from Python then.
What about those people *without* versioning issues?
I have no qualms suggesting that package manageme
MRAB wrote:
Sean Reifschneider wrote:
I'm mailing this to python-dev because I'd like feedback on the idea of
adding an "re" attribute to strings. I'm not sure if it's a good
idea or
not yet, but I figure it's worth discussion. The module mentioned here
includes a class called "restr()" whic
2009/7/4 Brett Cannon :
>> > While I really like the idea of using named branches for each release so
>> > that there is a single py3k branch that contains all relevant history
>> > for
>> > every release, I think we should start simple and go with cloned
>> > branches.
>> > That way the workflow d
