Hello,
Is someone able to make me a member of PAPT on Salsa, please?
Thanks.
Christopher
On Wed, 4 Sep 2019 at 20:51, Christopher Hoskin wrote:
>
> Hello,
>
> Please could I join PAPT in order to maintain a pympress package [1].
> I am a Debian Developer and already a member of DPMT. I have
Hi Andrey,
On Wed, Sep 11, 2019 at 07:32:33PM +0500, Andrey Rahmatullin wrote:
> > $ cycle
> > Traceback (most recent call last):
> > File "/usr/bin/cycle", line 12, in
> > from dialogs import *
> > File "/usr/share/cycle/dialogs.py", line 8, in
> > from cal_year import cycle, Val
>
On 9/10/19 7:50 AM, Andreas Tille wrote:
> Hi,
>
> in the process of the Python3 migration the package lefse was converted
> using 2to3.
Hi Andreas,
I wont comment on the relative import ambiguity problem, as Ghislain
replied correctly. However, I do want to comment on 2to3.
I generally
On 9/10/19 7:50 AM, Andreas Tille wrote:
> Hi,
>
> in the process of the Python3 migration the package lefse was converted
> using 2to3.
Hi Andreas,
I wont comment on the relative import ambiguity problem, as Ghislain
replied correctly. However, I do want to comment on 2to3.
I generally
Hi all,
On 12.09.19 08:30, Thomas Goirand wrote:
> I wont comment on the relative import ambiguity problem, as Ghislain
> replied correctly. However, I do want to comment on 2to3.
>
> I generally recommend against using it, in the favor of other tools.
...
>
> The advantage is that you'll get
Hi Michael,
On Thu, Sep 12, 2019 at 09:22:06AM +0200, Michael Kesper wrote:
> On 12.09.19 08:30, Thomas Goirand wrote:
> > I wont comment on the relative import ambiguity problem, as Ghislain
> > replied correctly. However, I do want to comment on 2to3.
> >
> > I generally recommend against
On 10.09.19 16:14, Ole Streicher wrote:
> Hi IOhannes,
>
> I have basically the same problem, funnily with almost the same subject:
which was entirely intentional :-)
i decided to start a new thread because i'm not sure whether the problem
is really the same.
but i guess, i'll just file a bug
On Thu, Sep 12, 2019 at 09:17:08AM +0200, Andreas Tille wrote:
> > > $ cycle
> > > Traceback (most recent call last):
> > > File "/usr/bin/cycle", line 12, in
> > > from dialogs import *
> > > File "/usr/share/cycle/dialogs.py", line 8, in
> > > from cal_year import cycle, Val
> > >
On Thu, Sep 12, 2019 at 08:30:20AM +0200, Thomas Goirand wrote:
> I wont comment on the relative import ambiguity problem, as Ghislain
> replied correctly. However, I do want to comment on 2to3.
>
> I generally recommend against using it, in the favor of other tools. For
> example, you can use
On Thu, Sep 12, 2019 at 01:57:32PM +0500, Andrey Rahmatullin wrote:
> > > There are circular imports in the code so you most likely broke that by
> > > reordering imports in various files.
> >
> > s/you most likely broke/2to3 most likely broke/
> 2to3 doesn't do that. You mentioned autopep8, it
Hi!
Often I stumble on this readthedocs.io [1] website and it's badly outdated.
Since we already have the Debian Wiki, I'm not sure it's worth keeping
up to date, or at least no one has cared to do so in the last 4 years.
If we really want a sphinx website, we should just build one on Salsa [2].
https://python3statement.org/ is a site documenting the projects which
are supporting the policy of dropping Python2 to keep Python3 only.
The site is designed for python packages specifically, to have only
Python3 supported by end of 2020.
But it seems to me it would be in the spirit of the
Drew Parsons writes ("should Debian add itself to https://python3statement.org
?"):
> https://python3statement.org/ is a site documenting the projects which
> are supporting the policy of dropping Python2 to keep Python3 only.
That statement is a *pledge* to drop support for python2 by the end
Package: sponsorship-requests
Severity: wishlist
Owner: Emmanuel Arias
X-Debbugs-CC: debian-python@lists.debian.org
Dear mentors,
I am looking for a sponsor for my package "flask-jwt-simple"
* Package name: flask-jwt-simple
Version : 0.0.3-1
Upstream Author : Landon
Hi,
On 12-09-2019 17:01, Ian Jackson wrote:
> But we need to be clear what's going on and communicate early.
Yes, not on the front page, but there is (first bullet):
https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html#deprecated-components
Paul
signature.asc
Hi Drew,
https://release.debian.org/transitions/html/python2-rm.html
Given the current progress it looks not easy to make a promise.
If some upstream happen to lag behind the schedule of python3
migration, we'll just stuck there for a while.
On 2019-09-12 14:46, Drew Parsons wrote:
>
On 12.09.19 17:01, Ian Jackson wrote:
Drew Parsons writes ("should Debian add itself to https://python3statement.org
?"):
https://python3statement.org/ is a site documenting the projects which
are supporting the policy of dropping Python2 to keep Python3 only.
That statement is a *pledge*
Hi,
On 12.09.19 16:09, Andreas Tille wrote:
> May be some final helping hint could be how to fix leaving the
> program that leads to:
>
>
> Traceback (most recent call last): File "/usr/bin/cycle", line 83,
> in OnCloseWindow Save_Cycle(cycle.name, cycle.passwd, cycle.file)
> File
but this leads later to
Traceback (most recent call last):
File "cycle.py", line 83, in OnCloseWindow
Save_Cycle(cycle.name, cycle.passwd, cycle.file)
File "/home/andreas/debian-maintain/salsa/med-team/cycle/save_load.py", line
46, in Save_Cycle
tmp=rt.encrypt(
19 matches
Mail list logo
