"Jakub Wilk" wrote:
>* Scott Kitterman , 2010-05-26, 17:43:
>>I means that the support tools for Python 3 should run in Python 3 As
>>an example, I've done a first cut at py3versions:
>>
>>http://www.kitterman.com/debian/
>
>Some remarks:
>
>- We probably want to get rid of "try: ... except Im
"Lino Mastrodomenico" wrote:
>2010/5/26 Scott Kitterman :
>> This would mean separate python-foo and python3-foo binaries where both are
>> supported from the same source.
>
>What will happen in the not-so-close future when Python 2.x is no
>longer supported? All the python3-foo binary packages
2010/5/26 Scott Kitterman :
> This would mean separate python-foo and python3-foo binaries where both are
> supported from the same source.
What will happen in the not-so-close future when Python 2.x is no
longer supported? All the python3-foo binary packages will be renamed
python-foo?
--
Lino
* Scott Kitterman , 2010-05-26, 17:43:
I means that the support tools for Python 3 should run in Python 3 As
an example, I've done a first cut at py3versions:
http://www.kitterman.com/debian/
Some remarks:
- We probably want to get rid of "try: ... except ImportError: ..."
compatibility tri
Hi Scott,
thanks for bringing this up.
On Wed, May 26, 2010 at 23:43, Scott Kitterman wrote:
> This has been discussed a bit, but I'd like to see where Debian Python
> consensus is on this.
>
> I think users who don't care about Python 3 yet, should be able to have
> systems that don't pull any P
[Scott Kitterman, 2010-05-26]
> This would mean separate python-foo and python3-foo binaries where both are
> supported from the same source.
Can we agree to use "python3-foo" schema for *all* packages with Python
3.X modules? (I'm lazy and I want to reject RFS mails even faster -
noticing python
Il 26/05/2010 23.43, Scott Kitterman ha scritto:
> This would mean separate python-foo and python3-foo binaries where both are
> supported from the same source.
>
> It would mean that binaries should not depend on both Python 2 and Python 3
> interpreters.
ACK.
Having a safety new provided by N
On May 26, 2010, at 05:43 PM, Scott Kitterman wrote:
>I think it makes sense for them to be kept separate at runtime.
>
>This would mean separate python-foo and python3-foo binaries where both are
>supported from the same source.
>
>It would mean that binaries should not depend on both Python 2 a
* Scott Kitterman , 2010-05-26, 17:43:
I think users who don't care about Python 3 yet, should be able to have
systems that don't pull any Python 3 elements on by accident. Python 3
is primarily of interest to developers right now and most users won't
care to have it.
It is very unusual for
This has been discussed a bit, but I'd like to see where Debian Python
consensus is on this.
I think users who don't care about Python 3 yet, should be able to have
systems that don't pull any Python 3 elements on by accident. Python 3 is
primarily of interest to developers right now and most
10 matches
Mail list logo
