On Wed, Nov 23, 2022 at 12:21:38AM +0100, Thomas Goirand wrote:
> On 11/22/22 17:59, Julian Gilbey wrote:
> > > > Or should we mark them as X-Python3-Version: << 3.11 so they can stay in
> > > > testing as long as Python 3.10 is the default?
> > >
> > > I don't think this is the way.
> >
> > I'm
On 11/22/22 17:59, Julian Gilbey wrote:
Or should we mark them as X-Python3-Version: << 3.11 so they can stay in
testing as long as Python 3.10 is the default?
I don't think this is the way.
I'm sorry, I don't understand - which is not the way?
I don't think you should "mark them as X-Pytho
On Tue, Nov 22, 2022 at 05:01:03PM +0100, Thomas Goirand wrote:
> > If there are people with the expertise to help upstream update
> > bytecode and parso (and probably several other low-level packages) for
> > 3.11 so that the software that depends on them works with 3.11, then
> > fine. (And it i
On 11/22/22 10:59, Julian Gilbey wrote:
On Tue, Nov 22, 2022 at 09:22:05AM +0100, Thomas Goirand wrote:
this, 100 times
I very much don't agree. I think it's going pretty well, and the number of
breakage isn't high. We just need a little bit of effort to make it in good
enough shape.
[...]
Now
On Monday, November 21, 2022 12:25:05 PM EST Scott Kitterman wrote:
> On November 21, 2022 5:02:57 PM UTC, "Louis-Philippe Véronneau"
wrote:
> >On 2022-11-21 02 h 08, Julian Gilbey wrote:
> >> I'm just flagging this up here, with a question about how we should
> >> proceed. Certainly we are not
On Tue, Nov 22, 2022 at 09:22:05AM +0100, Thomas Goirand wrote:
> > this, 100 times
>
> I very much don't agree. I think it's going pretty well, and the number of
> breakage isn't high. We just need a little bit of effort to make it in good
> enough shape.
> [...]
> Now, out of *many* of my packag
On 11/21/22 18:30, Sandro Tosi wrote:
On Mon, Nov 21, 2022 at 12:03 PM Louis-Philippe Véronneau
wrote:
On 2022-11-21 02 h 08, Julian Gilbey wrote:
I'm just flagging this up here, with a question about how we should
proceed. Certainly we are not ready to make Python 3.11 the default
Python ve
On Mon, Nov 21, 2022 at 12:03 PM Louis-Philippe Véronneau
wrote:
>
> On 2022-11-21 02 h 08, Julian Gilbey wrote:
> > I'm just flagging this up here, with a question about how we should
> > proceed. Certainly we are not ready to make Python 3.11 the default
> > Python version!!
>
> This is a conce
On November 21, 2022 5:02:57 PM UTC, "Louis-Philippe Véronneau"
wrote:
>On 2022-11-21 02 h 08, Julian Gilbey wrote:
>> I'm just flagging this up here, with a question about how we should
>> proceed. Certainly we are not ready to make Python 3.11 the default
>> Python version!!
>
>This is a co
On 2022-11-21 02 h 08, Julian Gilbey wrote:
I'm just flagging this up here, with a question about how we should
proceed. Certainly we are not ready to make Python 3.11 the default
Python version!!
This is a concern I share and I think I've been pretty vocal about it.
I feel the state of pytho
I've been having a somewhat interesting time with the python3.11-add
transition. Python 3.11 has made some significant changes to its
bytecode representation, and also changed some of it's internal data
structures related to frames quite significantly.
In my corner of the Python world, several im
11 matches
Mail list logo