Le 13/06/2024 à 22:34, Pavel Sanda a écrit :
On Thu, Jun 13, 2024 at 07:08:01PM +0100, José Matos wrote:
Although modern terminals have more lines and rows (for example the
shell screen that I use have 236 rows by 90 lines) we need to set some
common ground.
So my question to you is: what do yo
On Thu, Jun 13, 2024 at 07:08:01PM +0100, José Matos wrote:
> Although modern terminals have more lines and rows (for example the
> shell screen that I use have 236 rows by 90 lines) we need to set some
> common ground.
>
> So my question to you is: what do you think that the limit should be?
Wha
Dear developers,
I would like to reformat the Python code. My major doubt is on what
it should be the maximum line size for Python code.
Traditional wisdom, coming from standard screens of the 80's set it to
80.
Two of the best used tools to reformat Python code, black and ruff, set
this limit
On Thu, Jun 13, 2024 at 07:08:01PM GMT, José Matos wrote:
> So my question to you is: what do you think that the limit should be?
>
> I do not mind to share this limit with the C++ code, after all most of
> the same rational applies.
No strong opinion, but I do think it should be consistent acro
On Thu, Jun 13, 2024 at 10:52:26AM +0100, José Matos wrote:
> On Wed, 2024-06-12 at 10:06 +0200, Pavel Sanda wrote:
> > Hi Jose,
> >
> > bumping p3 version requirements and dropping p2 should go into
> > RELEASE-NOTES and specific version should be fixed in
> > INSTALL/README...
> >
> > Pavel
>
On Thu, 2024-06-13 at 10:58 +0200, Pavel Sanda wrote:
> On Wed, Jun 12, 2024 at 07:09:19PM +0300, Udicoudco wrote:
> > As I see it, when show changes in output
> > is selected, the output is not even remotely close to the final
> > manuscript.
>
> Right, but that was not my point. What I mean is t
On Thu, 2024-06-13 at 10:41 +0200, Pavel Sanda wrote:
> I wouldn't have this courage :)
>
> You are joining the debate little late, but you can try to convince
> Jose to delay his version bumping towards end of the cycle. Your mint
> 18 lifetime ends with some 2-3 years IIRC, so you'll need to upd
On Wed, 2024-06-12 at 10:06 +0200, Pavel Sanda wrote:
> Hi Jose,
>
> bumping p3 version requirements and dropping p2 should go into
> RELEASE-NOTES and specific version should be fixed in
> INSTALL/README...
>
> Pavel
For the moment I updated the INSTALL document.
I moved up the reference to Py
On Wed, Jun 12, 2024 at 07:09:19PM +0300, Udicoudco wrote:
> As I see it, when show changes in output
> is selected, the output is not even remotely close to the final
> manuscript.
Right, but that was not my point. What I mean is that I just had to submit to a
journal reviewers revised version of
On Thu, Jun 13, 2024 at 06:39:21AM +0200, Kornel Benko wrote:
> And it was (for me) very handy to use my wife as a (involuntary) tester of
> the master build. So that seems over now.
I wouldn't have this courage :)
You are joining the debate little late, but you can try to convince Jose to
delay
10 matches
Mail list logo
