Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #11697 > unrolled thread

updating mechanize - help concerning tests with pybuild

Back to article view | Back to linux.debian.maint.python

Contents

  updating mechanize - help concerning tests with pybuild Norbert Preining <norbert@preining.info> - 2019-08-31 05:40 +0200
    Re: updating mechanize - help concerning tests with pybuild Andrey Rahmatullin <wrar@debian.org> - 2019-08-31 09:00 +0200
    Re: updating mechanize - help concerning tests with pybuild Dmitry Shachnev <mitya57@debian.org> - 2019-08-31 10:20 +0200
      Re: updating mechanize - help concerning tests with pybuild Dmitry Shachnev <mitya57@debian.org> - 2019-08-31 18:00 +0200
        Re: updating mechanize - help concerning tests with pybuild Dmitry Shachnev <mitya57@debian.org> - 2019-08-31 18:10 +0200
          Re: updating mechanize - help concerning tests with pybuild Norbert Preining <norbert@preining.info> - 2019-08-31 18:50 +0200
      Re: updating mechanize - help concerning tests with pybuild Norbert Preining <norbert@preining.info> - 2019-08-31 18:00 +0200
    Re: updating mechanize - help concerning tests with pybuild Raphael Hertzog <hertzog@debian.org> - 2019-08-31 19:20 +0200
      Re: updating mechanize - help concerning tests with pybuild Norbert Preining <norbert@preining.info> - 2019-08-31 19:50 +0200
        Re: updating mechanize - help concerning tests with pybuild Raphael Hertzog <hertzog@debian.org> - 2019-08-31 21:00 +0200
          Re: updating mechanize - help concerning tests with pybuild Norbert Preining <norbert@preining.info> - 2019-09-01 02:20 +0200
            Re: updating mechanize - help concerning tests with pybuild Matthias Klose <doko@debian.org> - 2019-09-01 02:50 +0200
              Re: updating mechanize - help concerning tests with pybuild Norbert Preining <norbert@preining.info> - 2019-09-01 03:30 +0200
                Re: updating mechanize - help concerning tests with pybuild Raphael Hertzog <hertzog@debian.org> - 2019-09-01 10:10 +0200
                  Re: updating mechanize - help concerning tests with pybuild Norbert Preining <norbert@preining.info> - 2019-09-01 13:50 +0200
                    Re: updating mechanize - help concerning tests with pybuild Norbert Preining <norbert@preining.info> - 2019-09-01 15:40 +0200
      Re: updating mechanize - help concerning tests with pybuild Andrey Rahmatullin <wrar@debian.org> - 2019-08-31 19:50 +0200
    Re: updating mechanize - help concerning tests with pybuild Arnaud Fontaine <arnau@debian.org> - 2019-09-02 07:20 +0200
      Re: updating mechanize - help concerning tests with pybuild Norbert Preining <norbert@preining.info> - 2019-09-02 07:40 +0200

#11697 — updating mechanize - help concerning tests with pybuild

Dear all,

here are two questions: one concerning adopting/updating mechanize and
how to deal with rdepends, one concerning how to fix tests with special
requirements in pybuild.

For calibre and porting to python3, I need mechanize for python3.
The current version of python-mechanize is from 2012 and version 0.2.5,
while the latest version is 0.4.3 from a few days ago.

The recent versions support python3, so I would like to update
mechanize.

I checked the rdepends of python-mechanize:
  python-twill
  zope2.13
  python-zope.testbrowser
  calibre
  python-clientform

zope2.13 is very old, removed from testing, unmaintained
python-zope.testbrowser the same
python-clientform is a transitional package build from mechanize
python-twill has a last upload in 2016, but is lagging behind badly
(current version 1.8 on pypi)
calibre needs an updated mechanize.

So I think it would be fine to simply update mechanize without too much
troubles.

The current maintainers/uploaders are
Maintainer: Debian/Ubuntu Zope Team <pkg-zope-developers@lists.alioth.debian.org>
Uploaders: Brian Sutherland <brian@vanguardistas.net>,
           Fabio Tranchitella <kobold@debian.org>,
           Jérémy Bobbio <lunar@debian.org>,
           Matthias Klose <doko@ubuntu.com>,
           Arnaud Fontaine <arnau@debian.org>
(In CC, but Brian removed, he already declared he does not want to
maintain the package anymore, see bug #869439)

I would be interested in adopting mechanize if the current maintainers
/ uploaders are fine with it. Or we put it into the python modules team
and I do the stuff there. All is fine for me.

How could be proceed here?

---------------

Now for the pybuild question:

Current mechanize needs to set up a special environment for the tests.
There is a dedicated script
	run_tests.py
that would do the trick. I tried to use the pybuild before tests feature
to export PYTHONPATH, but that didn't work.

Is there a way to run a specific script instead of the built-in tests of
pybuild?

I thought about using PYTHON_DISABLE=tests and add a specific dh test
target. WDYT?

Thanks for any hints!

All the best

Norbert

--
PREINING Norbert                               http://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

[toc] | [next] | [standalone]

#11699

[Multipart message — attachments visible in raw view] — view raw

On Sat, Aug 31, 2019 at 11:33:54AM +0900, Norbert Preining wrote:
> here are two questions: one concerning adopting/updating mechanize and
> how to deal with rdepends, one concerning how to fix tests with special
> requirements in pybuild.
> 
> For calibre and porting to python3, I need mechanize for python3.
I'm sorry that I can't help with your questions, but what can you tell us
about Python 3 calibre? Last time I heard of it was famous "I am perfectly
capable of maintaining python 2 myself.  Far less work than migrating the
entire calibre codebase." from https://bugs.launchpad.net/calibre/+bug/1714107
I didn't read the recent comments on that bug but I found
https://github.com/kovidgoyal/calibre/blob/master/README.python3

-- 
WBR, wRAR

[toc] | [prev] | [next] | [standalone]

#11700

[Multipart message — attachments visible in raw view] — view raw

Hi Norbert,

Let me try answering your second question, about tests.

On Sat, Aug 31, 2019 at 11:33:54AM +0900, Norbert Preining wrote:
> Current mechanize needs to set up a special environment for the tests.
> There is a dedicated script
> run_tests.py
> that would do the trick. I tried to use the pybuild before tests feature
> to export PYTHONPATH, but that didn't work.
>
> Is there a way to run a specific script instead of the built-in tests of
> pybuild?

Something like this should do the trick:

- Add run_tests.py and the tests themselves to debian/pybuild.testfiles,
  to make pybuild copy them to the build directory.

- Add override_dh_auto_test target with a command like this:
  dh_auto_test -- --system custom --test-args "{interpreter} run_tests.py"

Then pybuild will take care of running the tests with all supported
interpreters, each one in its own directory, and cleaning up after that.

See pybuild(1) for details.

--
Dmitry Shachnev

[toc] | [prev] | [next] | [standalone]

#11704

[Multipart message — attachments visible in raw view] — view raw

On Sun, Sep 01, 2019 at 12:34:02AM +0900, Norbert Preining wrote:
> Now, the interesting thing are the error messages. One of them is
> [...]
> httperror_seek_wrapper: HTTP Error 403: request disallowed by robots.txt

Maybe this happens because pybuild exports http_proxy='http://127.0.0.1:9/',
and this breaks the local http server used in tests.

If you explicitly set http_proxy to empty string then pybuild won't do it.

> Huuuu? Why does it use the original file directly in mechanize.git???

Apparently you need to explicitly cd to build directory. So try this:

http_proxy= dh_auto_test -- --system custom --test-args "cd {build_dir}; {interpreter} run_tests.py"

With this command, only three tests are failing for me.

--
Dmitry Shachnev

[toc] | [prev] | [next] | [standalone]

#11707

[Multipart message — attachments visible in raw view] — view raw

On Sat, Aug 31, 2019 at 06:57:23PM +0300, Dmitry Shachnev wrote:
> On Sun, Sep 01, 2019 at 12:34:02AM +0900, Norbert Preining wrote:
> > Now, the interesting thing are the error messages. One of them is
> > [...]
> > httperror_seek_wrapper: HTTP Error 403: request disallowed by robots.txt
>
> Maybe this happens because pybuild exports http_proxy='http://127.0.0.1:9/',
> and this breaks the local http server used in tests.
>
> If you explicitly set http_proxy to empty string then pybuild won't do it.
>
> > Huuuu? Why does it use the original file directly in mechanize.git???
>
> Apparently you need to explicitly cd to build directory. So try this:
>
> http_proxy= dh_auto_test -- --system custom --test-args "cd {build_dir}; {interpreter} run_tests.py"
>
> With this command, only three tests are failing for me.

Ah, if you also add no_proxy= then all tests pass.

http_proxy= no_proxy= dh_auto_test -- --system custom --test-args "cd {build_dir}; {interpreter} run_tests.py"

--
Dmitry Shachnev

[toc] | [prev] | [next] | [standalone]

#11709

On Sat, 31 Aug 2019, Dmitry Shachnev wrote:
> http_proxy= no_proxy= dh_auto_test -- --system custom --test-args "cd {build_dir}; {interpreter} run_tests.py"

Cool, thanks a big lot!!!!

BTW, why isn't that mentioned anywhere in the pybuild docs ...

Thanks

Norbert

--
PREINING Norbert                               http://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

[toc] | [prev] | [next] | [standalone]

#11706

Dear Dmitry

thanks for your email!

On Sat, 31 Aug 2019, Dmitry Shachnev wrote:
> - Add run_tests.py and the tests themselves to debian/pybuild.testfiles,
>   to make pybuild copy them to the build directory.
> 
> - Add override_dh_auto_test target with a command like this:
>   dh_auto_test -- --system custom --test-args "{interpreter} run_tests.py"

Ok, I have done this and added the necessary files. Interestingly, I
*still* get errors:

Testing manually in the root:
$ pwd
.../mechanize.git
$ ls
... examples mechanize test test-tools ...
$ python2.7 run_tests.py
...............................................................................................................................................................................................................................................................................................................
----------------------------------------------------------------------
Ran 303 tests in 6.048s

OK


Testing manually in the build directory 
$ pwd
.../mechanize.git/.pybuild/cpython2_2.7_mechanize/build
$ ls
... examples mechanize test test-tools ...
$ python2.7 run_tests.py 
...............................................................................................................................................................................................................................................................................................................
----------------------------------------------------------------------
Ran 303 tests in 5.960s

OK


Finally doing dpkg-buildpackage or whatever
   debian/rules override_dh_auto_test-indep
make[1]: Entering directory '/home/norbert/Development/calibre/mechanize.git'
dh_auto_test -- --system custom --test-args "{interpreter} run_tests.py"
	pybuild --test -i python{version} -p 2.7 --system custom --test-args "{interpreter} run_tests.py"
I: pybuild base:217: python2.7 run_tests.py
.................................................................................................................................................................E...EEEEEEE.EEF.E.EEE.EE.EEEEEEEEEE..................................................................................FF.......................


Now, the interesting thing are the error messages. One of them is

ERROR: test_mozilla_cookiejar (test.test_functional.CookieJarTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/norbert/Development/calibre/mechanize.git/test/test_functional.py", line 684, in test_mozilla_cookiejar
    self._test_cookiejar(make_cookiejar, commit)
  File "/home/norbert/Development/calibre/mechanize.git/test/test_functional.py", line 654, in _test_cookiejar
    html = br.open(url).read()
  File "/home/norbert/Development/calibre/mechanize.git/mechanize/_mechanize.py", line 253, in open
    return self._mech_open(url_or_request, data, timeout=timeout)
  File "/home/norbert/Development/calibre/mechanize.git/mechanize/_mechanize.py", line 309, in _mech_open
    raise response
httperror_seek_wrapper: HTTP Error 403: request disallowed by robots.txt


Huuuu? Why does it use the original file directly in mechanize.git???

run_tests.py does more or less
    this_dir = os.path.dirname(__file__)
    sys.path.insert(0, os.path.join(this_dir, "test"))
    sys.path.insert(0, os.path.join(this_dir, "test-tools"))
    sys.path.insert(0, os.path.join(this_dir, "mechanize"))
so **why** does it use the test/test-tools/mechanize from the ROOT
instead of the python test build?

It seems something is messed up in the pybuild test setup?

If you want to take a look, here is the git repo with the current
status:
	https://github.com/norbusan/debian-mechanize.git

Thanks a lot and all the best

Norbert

--
PREINING Norbert                               http://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

[toc] | [prev] | [next] | [standalone]

#11710

Hello,

On Sat, 31 Aug 2019, Norbert Preining wrote:
> I would be interested in adopting mechanize if the current maintainers
> / uploaders are fine with it. Or we put it into the python modules team
> and I do the stuff there. All is fine for me.

I would like to see the package in the python modules team as well. We
have packages in Kali depending on this module and we also need the Python
3 version.

Hence we also pinged the current maintainers here just one day before you:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912014#10

> How could be proceed here?

Looking at the status of the packages in the team, it's quite clear that
the team is MIA as a whole:
https://qa.debian.org/developer.php?email=pkg-zope-developers@lists.alioth.debian.org

The only recent upload is from TANIGUCHI Takaki <takaki@debian.org>
on zope.deprecation 4.4.0-1. It's also the only package

Thus I would suggest to go ahead and take over the package in the DPMT
team.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

[toc] | [prev] | [next] | [standalone]

#11711

Hi Raphael,

On Sat, 31 Aug 2019, Raphael Hertzog wrote:
> Thus I would suggest to go ahead and take over the package in the DPMT
> team.

Fine with me. If you could give me DPMT membership on salsa I can push
my current work there.

Do we go through package salvaging?
https://wiki.debian.org/PackageSalvaging

Best

Norbert

--
PREINING Norbert                               http://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

[toc] | [prev] | [next] | [standalone]

#11713

Hi,

On Sun, 01 Sep 2019, Norbert Preining wrote:
> Fine with me. If you could give me DPMT membership on salsa I can push
> my current work there.

I can't grant you the right to the whole group (I'm not an owner) but
I created the repository and granted you the rights on this repository
at least:
https://salsa.debian.org/python-team/modules/python-mechanize

Let me know if you need anything else.

To get access to the group, you should follow the procedure described
in this document:
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst

> Do we go through package salvaging?
> https://wiki.debian.org/PackageSalvaging

I don't think it's required here. The bugs have been open for long enough
without any activity.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

[toc] | [prev] | [next] | [standalone]

#11715

Hi Raphael,

@Matthias, please read on.

On Sat, 31 Aug 2019, Raphael Hertzog wrote:
> https://salsa.debian.org/python-team/modules/python-mechanize

Thanks, that is perfect. I pushed my work there, changed control VCS,
maintainer, and uploader.

ATM I only put me into the uploaders. Please, those who are interested,
put yourself in there, thanks!

> > Do we go through package salvaging?
> > https://wiki.debian.org/PackageSalvaging
> 
> I don't think it's required here. The bugs have been open for long enough
> without any activity.

Hmmm... I don't feel confident simply uploading someone's else package.
Best would probably be if Matthias Klose, one of the current Uploaders,
agrees to that and uploads the current package thus passing over
maintainership.

Matthias?

Best

Norbert

--
PREINING Norbert                               http://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

[toc] | [prev] | [next] | [standalone]

#11716

On 01.09.19 01:59, Norbert Preining wrote:
> Hi Raphael,
> 
> @Matthias, please read on.
> 
> On Sat, 31 Aug 2019, Raphael Hertzog wrote:
>> https://salsa.debian.org/python-team/modules/python-mechanize
> 
> Thanks, that is perfect. I pushed my work there, changed control VCS,
> maintainer, and uploader.
> 
> ATM I only put me into the uploaders. Please, those who are interested,
> put yourself in there, thanks!
> 
>>> Do we go through package salvaging?
>>> https://wiki.debian.org/PackageSalvaging
>>
>> I don't think it's required here. The bugs have been open for long enough
>> without any activity.
> 
> Hmmm... I don't feel confident simply uploading someone's else package.
> Best would probably be if Matthias Klose, one of the current Uploaders,
> agrees to that and uploads the current package thus passing over
> maintainership.
> 
> Matthias?

did you see my comment in #936270?

[toc] | [prev] | [next] | [standalone]

#11717

[Multipart message — attachments visible in raw view] — view raw

Dear Matthias

Thanks, I interpret this a go ahead with the adoption.

Thanks for your and the teams work.

At all: anything you want to see before I upload the new version?

Best

Norbert

On September 1, 2019 9:43:33 AM GMT+09:00, Matthias Klose <doko@debian.org> wrote:
>On 01.09.19 01:59, Norbert Preining wrote:
>> Hi Raphael,
>> 
>> @Matthias, please read on.
>> 
>> On Sat, 31 Aug 2019, Raphael Hertzog wrote:
>>> https://salsa.debian.org/python-team/modules/python-mechanize
>> 
>> Thanks, that is perfect. I pushed my work there, changed control VCS,
>> maintainer, and uploader.
>> 
>> ATM I only put me into the uploaders. Please, those who are
>interested,
>> put yourself in there, thanks!
>> 
>>>> Do we go through package salvaging?
>>>> https://wiki.debian.org/PackageSalvaging
>>>
>>> I don't think it's required here. The bugs have been open for long
>enough
>>> without any activity.
>> 
>> Hmmm... I don't feel confident simply uploading someone's else
>package.
>> Best would probably be if Matthias Klose, one of the current
>Uploaders,
>> agrees to that and uploads the current package thus passing over
>> maintainership.
>> 
>> Matthias?
>
>did you see my comment in #936270?


--
PREINING Norbert http://www.preining.info
Accelia Inc. + JAIST + TeX Live + Debian Developer
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

[toc] | [prev] | [next] | [standalone]

#11719

Hi,

On Sun, 01 Sep 2019, Norbert Preining wrote:
> At all: anything you want to see before I upload the new version?

I checked the package quickly (without building it), it looks good.
Maybe you could have bumped debhelper to 12 and standards-version to 4.4.0
but that's a minor detail.

Thanks for leading this!

Cheers,

> On September 1, 2019 9:43:33 AM GMT+09:00, Matthias Klose <doko@debian.org> wrote:
> >On 01.09.19 01:59, Norbert Preining wrote:
> >> Hi Raphael,
> >> 
> >> @Matthias, please read on.
> >> 
> >> On Sat, 31 Aug 2019, Raphael Hertzog wrote:
> >>> https://salsa.debian.org/python-team/modules/python-mechanize
> >> 
> >> Thanks, that is perfect. I pushed my work there, changed control VCS,
> >> maintainer, and uploader.
> >> 
> >> ATM I only put me into the uploaders. Please, those who are
> >interested,
> >> put yourself in there, thanks!
> >> 
> >>>> Do we go through package salvaging?
> >>>> https://wiki.debian.org/PackageSalvaging
> >>>
> >>> I don't think it's required here. The bugs have been open for long
> >enough
> >>> without any activity.
> >> 
> >> Hmmm... I don't feel confident simply uploading someone's else
> >package.
> >> Best would probably be if Matthias Klose, one of the current
> >Uploaders,
> >> agrees to that and uploads the current package thus passing over
> >> maintainership.
> >> 
> >> Matthias?
> >
> >did you see my comment in #936270?
> 
> 
> --
> PREINING Norbert http://www.preining.info
> Accelia Inc. + JAIST + TeX Live + Debian Developer
> GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

[toc] | [prev] | [next] | [standalone]

#11721

Dear Raphael,

> Maybe you could have bumped debhelper to 12 and standards-version to 4.4.0

Done that now, and removed the last lintian warning.

Uploading later today.

All the best

Norbert

--
PREINING Norbert                               http://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

[toc] | [prev] | [next] | [standalone]

#11722

Hi all,

On Sun, 01 Sep 2019, Norbert Preining wrote:
> Done that now, and removed the last lintian warning.

And now also
- fixed building in clean chroot (missing build deps for tests and run)
- install docs made via sphinx
- updated copyright file to match what is advertised in the package

Package is uploaded to experimental as it needs to go through NEW queue
... oh holy ????, uploads that need the NEW queue need to include the
binaries, right?

<rant on>
Advertising source only uploads and then requiring NEW queue processing
to include binaries is **really** ?#$(&#$(&#
<rant off>

Will see what dak tells me about it.

Best

Norbert

--
PREINING Norbert                               http://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

[toc] | [prev] | [next] | [standalone]

#11712

[Multipart message — attachments visible in raw view] — view raw

On Sat, Aug 31, 2019 at 07:10:43PM +0200, Raphael Hertzog wrote:
> Looking at the status of the packages in the team, it's quite clear that
> the team is MIA as a whole:
> https://qa.debian.org/developer.php?email=pkg-zope-developers@lists.alioth.debian.org
> 
> The only recent upload is from TANIGUCHI Takaki <takaki@debian.org>
> on zope.deprecation 4.4.0-1. It's also the only package
> 
> Thus I would suggest to go ahead and take over the package in the DPMT
> team.
And many of those packages can be RMed. I checked packages from `grep-dctrl
-FMaintainer pkg-zope`.

These non-zope.* packages have revdeps:

python-chameleon
python-mechanize (while python-clientform can be dropped)
python-transaction
python-zc.buildout
python-zconfig
python-zdaemon
python-zodb

So these non-zope.* packages can be RMed:

bobo
sourcecodegen
van.pydeb

It's harder to check all revdeps of the zope.* packages as they depend on
each other and some, but not all, have py3 subpackages, but these py2
subpackages can be dropped (I didn't check if they are the only
subpackages):

python-zope.authentication
python-zope.cachedescriptors
python-zope.component-persistentregistry
python-zope.component-test
python-zope.copy
python-zope.dottedname
python-zope.sendmail
python-zope.sqlalchemy
python-zope.testbrowser
python-zope.traversing

And these source packages can be RMed (overlaps with the list above,
checked with dak):

zope.authentication
zope.browser
zope.cachedescriptors
zope.contenttype
zope.copy
zope.dottedname
zope.i18n
zope.publisher
zope.sendmail
zope.sqlalchemy
zope.testbrowser
zope.traversing

This includes several Py3 subpackages.

Hope this helps.

-- 
WBR, wRAR

[toc] | [prev] | [next] | [standalone]

#11735

Hi,

> The current maintainers/uploaders are
> Maintainer: Debian/Ubuntu Zope Team <pkg-zope-developers@lists.alioth.debian.org>
> Uploaders: Brian Sutherland <brian@vanguardistas.net>,
>            Fabio Tranchitella <kobold@debian.org>,
>            Jérémy Bobbio <lunar@debian.org>,
>            Matthias Klose <doko@ubuntu.com>,
>            Arnaud Fontaine <arnau@debian.org>
> (In CC, but Brian removed, he already declared he does not want to
> maintain the package anymore, see bug #869439)
>
> I would be interested in adopting mechanize if the current maintainers
> / uploaders are fine with it. Or we put it into the python modules team
> and I do the stuff there. All is fine for me.

As I have  no plan to work on  it, I think it is better  if someone else
maintains it, so please go ahead and thanks for taking over maintenance!

Regards,
-- 
Arnaud Fontaine

[toc] | [prev] | [next] | [standalone]

#11736

Dear Arnaud,

thanks a lot for agreeing, and all your work on mechanize!

All the best

Norbert

On Mon, 02 Sep 2019, Arnaud Fontaine wrote:
> As I have  no plan to work on  it, I think it is better  if someone else
> maintains it, so please go ahead and thanks for taking over maintenance!

--
PREINING Norbert                               http://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web