Hi,
On Sat, 1 Sep 2018 12:43:27 +0200 Nicolas Dandrimont
wrote:
> > As a proof of concept I've gone and done the changes needed to pull
> this off on a fork of the git repo in my personal namespace.
>
> https://salsa.debian.org/olasd/astroid
>
> The astroid source package is in the master /
Control: tags -1 + patch
* Thomas Goirand [2018-08-25 22:02:51 +0200]:
> Hi Sando,
>
> I do support uploading 2 source packages, one for py2, and one for py3.
> This is the most reasonable solution. Worst case, if that cannot be
> done, then we got to move forward and restore Py3 support (and
Hi Sando,
I do support uploading 2 source packages, one for py2, and one for py3.
This is the most reasonable solution. Worst case, if that cannot be
done, then we got to move forward and restore Py3 support (and
eventually drop Py2), but I prefer the former solution.
The issue has been opened
Hi Sandro,
thanks for this update
On Thursday, 2 August 2018 12:39:18 AEST Sandro Tosi wrote:
> there are currently 2 source packages:
>
> astroid: on the 1.x branch, builds python-astroid and python3-astroid
> pylint: on the 1.x branch, builds pylint (depends on python-astroid),
> pylint3
Hi
I miss any description of the real problem. You only describe
solutions, but you forget to mention why the easiest solution, just
upgrade both sources, does not work. Sure, some of the points can be
found in the bug report.
On Thu, Aug 02, 2018 at 12:39:18PM -0400, Sandro Tosi wrote:
>
Le jeudi 02 août 2018 à 19:32:15+0200, Bastian Blank a écrit :
> [why should one package two source packages?]
See [1] and following posts. astroid 2.0 dropped the support for Python2.
Regards,
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902631#77
--
Pierre-Elliott Bécue
GPG: 9AE0
Le jeudi 02 août 2018 à 12:39:18-0400, Sandro Tosi a écrit :
> there are currently 2 source packages:
>
> astroid: on the 1.x branch, builds python-astroid and python3-astroid
> pylint: on the 1.x branch, builds pylint (depends on python-astroid),
> pylint3 (depends on python3-astroid),
there are currently 2 source packages:
astroid: on the 1.x branch, builds python-astroid and python3-astroid
pylint: on the 1.x branch, builds pylint (depends on python-astroid),
pylint3 (depends on python3-astroid), pylint-doc
the only way forward to keep compat with python2 while supporting
Le dimanche 22 juillet 2018 à 20:43:02-0400, Sandro Tosi a écrit :
> On Sun, Jul 22, 2018 at 8:31 PM Mattia Rizzolo wrote:
> >
> > On Sun, Jul 22, 2018 at 03:52:04PM -0400, Sandro Tosi wrote:
> > > thanks for ignoring the next paragraph in that email, so let me re-add it
> > > here:
> >
> > I
On Sun, Jul 22, 2018 at 8:31 PM Mattia Rizzolo wrote:
>
> On Sun, Jul 22, 2018 at 03:52:04PM -0400, Sandro Tosi wrote:
> > thanks for ignoring the next paragraph in that email, so let me re-add it
> > here:
>
> I didn't ignore it, I explicitly picked on your first, fairly taunting,
> and
On Sun, Jul 22, 2018 at 03:52:04PM -0400, Sandro Tosi wrote:
> thanks for ignoring the next paragraph in that email, so let me re-add it
> here:
I didn't ignore it, I explicitly picked on your first, fairly taunting,
and inappropriately passive-aggressive sentence (like this one).
> since
> What do you mean with "support"? Astroid 2.0 is working properly with py3.7
> according to upstream.
i mean that pylint/astroid 2.0 do not work with python 2 at all, but
only with python 3.4 onwards (so yes, also 3.7 in that regards).
--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
> Upstream README seems to indicate that there is no release that supports
> *both* python 2.7 and 3.7
i know, that's exactly my point
> so this is not a choice between 2.0 and 1.9.
well it is: it can be decided to ignore the 2.x branch and stick with
1.9 for buster (which support python 2 and
Le 22 juillet 2018 21:52:04 GMT+02:00, Sandro Tosi a écrit :
>On Sat, Jul 21, 2018 at 6:58 AM Mattia Rizzolo
>wrote:
>>
>> On Tue, Jul 17, 2018 at 03:06:14PM -0400, Sandro Tosi wrote:
>> > no need, i can upgrade the package myself when needed, but thanks
>for the offer.
>>
>> Then can you pretty
Hi Sandro,
Upstream README seems to indicate that there is no release that supports
*both* python 2.7 and 3.7 so this is not a choice between 2.0 and 1.9.
More likely, two source packages are required for buster. Alternatively one of
Python 2 / Python 3 must be dropped from pylint (presumably
On Sat, Jul 21, 2018 at 6:58 AM Mattia Rizzolo wrote:
>
> On Tue, Jul 17, 2018 at 03:06:14PM -0400, Sandro Tosi wrote:
> > no need, i can upgrade the package myself when needed, but thanks for the
> > offer.
>
> Then can you pretty please do it? It is neeeded.
thanks for ignoring the next
On Tue, Jul 17, 2018 at 03:06:14PM -0400, Sandro Tosi wrote:
> no need, i can upgrade the package myself when needed, but thanks for the
> offer.
Then can you pretty please do it? It is neeeded.
signature.asc
Description: PGP signature
Le mardi 17 juillet 2018 à 15:06:14-0400, Sandro Tosi a écrit :
> no need, i can upgrade the package myself when needed, but thanks for the
> offer.
>
> since astroid/pylint only support python 3.4+, it is not as simple as
> package the new version and upload it; i'm not even (yet) sure buster
>
no need, i can upgrade the package myself when needed, but thanks for the offer.
since astroid/pylint only support python 3.4+, it is not as simple as
package the new version and upload it; i'm not even (yet) sure buster
should have 2.0 but maybe it should to 1.9
On Tue, Jul 17, 2018 at 2:41 PM
Le dimanche 08 juillet 2018 à 06:44:56-0400, Sandro Tosi a écrit :
> Why don't you just submit it?
Because it's not finished yet.
--
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.
Why don't you just submit it?
On Sun, Jul 8, 2018, 06:24 Pierre-Elliott Bécue wrote:
> Hi, Sandro,
>
> Would you agree to review and upload a fix I'd submit for Bug#902631?
>
> If you don't have enough time, may I have a fix uploaded myself?
>
> Cheers and wish you well! :)
>
> --
>
Hi, Sandro,
Would you agree to review and upload a fix I'd submit for Bug#902631?
If you don't have enough time, may I have a fix uploaded myself?
Cheers and wish you well! :)
--
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2
It's far easier to fight for one's
Control: reassign -1 src:astroid
Control: retitle -1 Not compatible with Python 3.7
Control: tag -1 upstream
Control: affects -1 devscripts
On Thu, Jun 28, 2018 at 03:12:14PM -0400, Lev Lazinskiy wrote:
> The current CI process fails in unstable[1]. It appears to be due to Python
> 3.7 being
Package: devscripts
Version: 2.18.3
Severity: normal
Dear Maintainer,
The current CI process fails in unstable[1]. It appears to be due to Python
3.7 being released in the last few days[2].
The issue is:
: generator raised StopIteration
It can be reproduced by running:
python3.7 -m flake8
24 matches
Mail list logo
