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

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

Bug#729956: Forwarded upstream

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

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#729956: Forwarded upstream Andreas Tille <tille@debian.org> - 2017-09-06 22:30 +0200
    Bug#729956: Forwarded upstream Yuri D'Elia <wavexx@thregr.org> - 2017-09-06 22:40 +0200
      Bug#729956: Forwarded upstream Andreas Tille <tille@debian.org> - 2017-09-06 23:00 +0200
        Bug#729956: git-dpm (was Re: Bug#729956: Forwarded upstream) Yuri D'Elia <wavexx@thregr.org> - 2017-09-06 23:20 +0200
          Re: git-dpm (was Re: Bug#729956: Forwarded upstream) Scott Kitterman <debian@kitterman.com> - 2017-09-07 00:50 +0200
            Re: git-dpm (was Re: Bug#729956: Forwarded upstream) Brian May <brian@linuxpenguins.xyz> - 2017-09-07 01:20 +0200
              Re: git-dpm (was Re: Bug#729956: Forwarded upstream) Yuri D'Elia <wavexx@thregr.org> - 2017-09-08 00:50 +0200
            Re: git-dpm (was Re: Bug#729956: Forwarded upstream) Brian May <brian@linuxpenguins.xyz> - 2017-09-07 01:30 +0200
              Re: git-dpm (was Re: Bug#729956: Forwarded upstream) Scott Kitterman <debian@kitterman.com> - 2017-09-07 07:00 +0200
                Re: git-dpm (was Re: Bug#729956: Forwarded upstream) Brian May <brian@linuxpenguins.xyz> - 2017-09-07 07:30 +0200
    Bug#729956: Forwarded upstream Diane Trout <diane@ghic.org> - 2017-09-07 00:30 +0200
      Bug#729956: Forwarded upstream Matthias Klose <doko@debian.org> - 2017-09-07 06:20 +0200
      Bug#729956: Forwarded upstream Andreas Tille <andreas@an3as.eu> - 2017-09-07 06:30 +0200
        Bug#729956: Forwarded upstream Diane Trout <diane@ghic.org> - 2017-09-07 06:40 +0200
          Bug#729956: Forwarded upstream Andreas Tille <andreas@an3as.eu> - 2017-09-07 08:40 +0200
            Bug#729956: Forwarded upstream Diane Trout <diane@ghic.org> - 2017-09-08 08:40 +0200
    Bug#729956: Python 3 Statsmodels & Pandas Diane Trout <diane@ghic.org> - 2017-09-16 22:50 +0200
      Bug#729956: Python 3 Statsmodels & Pandas Yuri D'Elia <wavexx@thregr.org> - 2017-09-16 23:10 +0200
        Bug#729956: Python 3 Statsmodels & Pandas Diane Trout <diane@ghic.org> - 2017-09-16 23:30 +0200
          Bug#729956: Python 3 Statsmodels & Pandas Yuri D'Elia <wavexx@thregr.org> - 2017-09-17 00:00 +0200
            Re: skimage (was: Re: Bug#729956: Python 3 Statsmodels & Pandas) Yaroslav Halchenko <yoh@debian.org> - 2017-10-13 00:10 +0200
            skimage (was: Re: Bug#729956: Python 3 Statsmodels & Pandas) Yuri D'Elia <wavexx@thregr.org> - 2017-10-13 00:40 +0200
          Re: Python 3 Statsmodels & Pandas Stuart Prescott <stuart@debian.org> - 2017-09-18 04:00 +0200
            Re: Python 3 Statsmodels & Pandas Diane Trout <diane@ghic.org> - 2017-09-18 07:20 +0200
              Re: Python 3 Statsmodels & Pandas Stuart Prescott <stuart@debian.org> - 2017-09-18 10:10 +0200
                Re: Python 3 Statsmodels & Pandas Gordon Ball <gordon@chronitis.net> - 2017-09-18 19:30 +0200
                  Re: Python 3 Statsmodels & Pandas Matthias Klose <doko@debian.org> - 2017-09-18 21:30 +0200
                    Re: Python 3 Statsmodels & Pandas Diane Trout <diane@ghic.org> - 2017-09-19 06:50 +0200
                Re: Python 3 Statsmodels & Pandas Andreas Tille <andreas@an3as.eu> - 2017-09-21 16:30 +0200
                  Re: Python 3 Statsmodels & Pandas Ghislain Vaillant <ghisvail@gmail.com> - 2017-09-21 17:00 +0200
                  Re: Python 3 Statsmodels & Pandas Diane Trout <diane@ghic.org> - 2017-09-21 23:50 +0200
                    Re: Python 3 Statsmodels & Pandas Diane Trout <diane@ghic.org> - 2017-09-22 00:10 +0200
                      Re: Python 3 Statsmodels & Pandas Yaroslav Halchenko <debian@onerussian.com> - 2017-09-22 04:30 +0200
                        Re: Python 3 Statsmodels & Pandas Diane Trout <diane@ghic.org> - 2017-09-22 07:20 +0200
                          Re: Python 3 Statsmodels & Pandas Diane Trout <diane@ghic.org> - 2017-09-24 20:30 +0200
                            Re: Python 3 Statsmodels & Pandas Andreas Tille <andreas@fam-tille.de> - 2017-09-25 00:10 +0200
                              Re: Python 3 Statsmodels & Pandas Yaroslav Halchenko <debian@onerussian.com> - 2017-09-25 01:00 +0200
                                Re: Python 3 Statsmodels & Pandas Diane Trout <diane@ghic.org> - 2017-09-25 01:20 +0200
                            Re: Python 3 Statsmodels & Pandas Diane Trout <diane@ghic.org> - 2017-09-25 08:50 +0200
                              Re: Python 3 Statsmodels & Pandas Andreas Tille <andreas@an3as.eu> - 2017-09-25 09:50 +0200
                                Re: Python 3 Statsmodels & Pandas Diane Trout <diane@ghic.org> - 2017-09-25 19:40 +0200
                                  Re: Python 3 Statsmodels & Pandas Andreas Tille <andreas@an3as.eu> - 2017-09-25 19:50 +0200
                                Re: Python 3 Statsmodels & Pandas Diane Trout <diane@ghic.org> - 2017-09-26 06:40 +0200
                                  Re: Python 3 Statsmodels & Pandas Andreas Tille <andreas@fam-tille.de> - 2017-09-26 09:20 +0200
                                    Re: Python 3 Statsmodels & Pandas Diane Trout <diane@ghic.org> - 2017-09-26 20:40 +0200
                                      Re: Python 3 Statsmodels & Pandas Yaroslav Halchenko <debian@onerussian.com> - 2017-09-26 22:50 +0200
                                      Re: Python 3 Statsmodels & Pandas Andreas Tille <andreas@an3as.eu> - 2017-09-26 23:00 +0200
                                        Re: Python 3 Statsmodels & Pandas Diane Trout <diane@ghic.org> - 2017-09-26 23:50 +0200
                                          Re: Python 3 Statsmodels & Pandas Andreas Tille <andreas@fam-tille.de> - 2017-09-27 08:20 +0200
                                        Re: Python 3 Statsmodels & Pandas Diane Trout <diane@ghic.org> - 2017-09-27 07:50 +0200
                                          Re: Python 3 Statsmodels & Pandas Andreas Tille <andreas@fam-tille.de> - 2017-09-27 09:00 +0200
                                            Re: Python 3 Statsmodels & Pandas Diane Trout <diane@ghic.org> - 2017-09-27 09:30 +0200
                                              Re: Python 3 Statsmodels & Pandas Andreas Tille <andreas@an3as.eu> - 2017-09-27 10:10 +0200
                                                Re: Python 3 Statsmodels & Pandas Andreas Tille <andreas@an3as.eu> - 2017-09-27 12:20 +0200
                                                  Re: Python 3 Statsmodels & Pandas "Rebecca N. Palmer" <rebecca_palmer@zoho.com> - 2017-09-29 23:40 +0200
                                                    Re: Python 3 Statsmodels & Pandas Diane Trout <diane@ghic.org> - 2017-09-30 01:00 +0200
                                                      Re: Python 3 Statsmodels & Pandas "Rebecca N. Palmer" <rebecca_palmer@zoho.com> - 2017-09-30 10:20 +0200
                                                      Re: Python 3 Statsmodels & Pandas Ghislain Vaillant <ghisvail@gmail.com> - 2017-09-30 11:20 +0200
                                                      Re: Python 3 Statsmodels & Pandas Dmitry Shachnev <mitya57@debian.org> - 2017-09-30 11:30 +0200
                                                        Re: Python 3 Statsmodels & Pandas Diane Trout <diane@ghic.org> - 2017-09-30 18:00 +0200
                                                          Re: Python 3 Statsmodels & Pandas "Rebecca N. Palmer" <rebecca_palmer@zoho.com> - 2017-09-30 18:40 +0200
                        Re: Python 3 Statsmodels & Pandas Andreas Tille <andreas@an3as.eu> - 2017-09-22 08:20 +0200
                          Re: Python 3 Statsmodels & Pandas Yaroslav Halchenko <debian@onerussian.com> - 2017-09-23 16:10 +0200
                            Re: Python 3 Statsmodels & Pandas Andreas Tille <andreas@an3as.eu> - 2017-09-24 13:30 +0200
                              Re: Python 3 Statsmodels & Pandas Yaroslav Halchenko <debian@onerussian.com> - 2017-09-25 01:00 +0200
                    Re: Python 3 Statsmodels & Pandas Yaroslav Halchenko <yoh@onerussian.com> - 2017-09-22 00:20 +0200
                    Re: Python 3 Statsmodels & Pandas Piotr Ożarowski <piotr@debian.org> - 2017-09-22 11:00 +0200
                      Re: Python 3 Statsmodels & Pandas Diane Trout <diane@ghic.org> - 2017-09-22 21:40 +0200
                        Re: Python 3 Statsmodels & Pandas Ghislain Vaillant <ghisvail@gmail.com> - 2017-09-23 11:50 +0200
                      Re: Python 3 Statsmodels & Pandas Yaroslav Halchenko <debian@onerussian.com> - 2017-09-23 16:00 +0200
                        Re: Python 3 Statsmodels & Pandas Piotr Ożarowski <piotr@debian.org> - 2017-09-25 11:20 +0200
        Bug#729956: Python 3 Statsmodels & Pandas Matthias Klose <doko@debian.org> - 2017-09-17 11:20 +0200

Page 1 of 4  [1] 2 3 4  Next page →

#9789 — Bug#729956: Forwarded upstream

Hi,

On Wed, Sep 06, 2017 at 05:26:13PM +0200, Yuri D'Elia wrote:
> On Wed, Sep 06 2017, Andreas Tille wrote:
> > I opened an issue on Github
> >
> >     https://github.com/statsmodels/statsmodels/issues/3909
> >
> > requesting Python3 support.
> 
> I concur with what was said in the issue.
> This is only an issue with debian's packaging.
> 
> I've been using a custom build of statsmodels on python3 since years
> as well without problems.

Great.  What about sending a patch with your changes to the bug
report?  I've added a branch debian-python3 to

   https://anonscm.debian.org/git/debian-science/packages/statsmodels.git

but the build failed (for other reasons).  I'd willing to work on this
but I definitely need help since I'm lacking the needed Python
knowledge.

Kind regards

      Andreas.

-- 
http://fam-tille.de

[toc] | [next] | [standalone]

#9790

On Wed, Sep 06 2017, Andreas Tille wrote:
> Great.  What about sending a patch with your changes to the bug
> report?  I've added a branch debian-python3 to

I always built from source, not with the debian packaging.

>    https://anonscm.debian.org/git/debian-science/packages/statsmodels.git
>
> but the build failed (for other reasons).  I'd willing to work on this
> but I definitely need help since I'm lacking the needed Python
> knowledge.

Hum, I always assumed the consensus on python packages was to manage
them with git-dpm, which is something I cannot digest (and has stopped
me from contributing more).

But just to confirm, I see that statsmodels is just using
git-buildpackage?

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

#9791

Hi Yuri,

On Wed, Sep 06, 2017 at 10:35:57PM +0200, Yuri D'Elia wrote:
> I always built from source, not with the debian packaging.
> 
> >    https://anonscm.debian.org/git/debian-science/packages/statsmodels.git
> >
> > but the build failed (for other reasons).  I'd willing to work on this
> > but I definitely need help since I'm lacking the needed Python
> > knowledge.
> 
> Hum, I always assumed the consensus on python packages was to manage
> them with git-dpm, which is something I cannot digest (and has stopped
> me from contributing more).
> 
> But just to confirm, I see that statsmodels is just using
> git-buildpackage?

Yes.
 
Kind regards

    Andreas.

-- 
http://fam-tille.de

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

#9792 — Bug#729956: git-dpm (was Re: Bug#729956: Forwarded upstream)

On Wed, Sep 06 2017, Andreas Tille wrote:
>> But just to confirm, I see that statsmodels is just using
>> git-buildpackage?
>
> Yes.

Ok, that's reassuring. I'll have a look at the packaging, since I'm
already on alioth.

But since DPMT is CC-ed (I normally follow via gmane), I take the
occasion to say that I _really_ _REALLY_ wished the recommendation on
git-dpm to be reconsidered, or at least relaxed.

For a newcomer, git-dpm is overkill and underdocumented.
From an outsider, making a Debian package already looks daunting.
git-dpm does not help.

On the other hand, git-buildpackage is a relatively smooth progression
from quilt, and it does provide some added convenience.

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

#9794 — Re: git-dpm (was Re: Bug#729956: Forwarded upstream)

On September 6, 2017 5:16:13 PM EDT, Yuri D'Elia <wavexx@thregr.org> wrote:
>On Wed, Sep 06 2017, Andreas Tille wrote:
>>> But just to confirm, I see that statsmodels is just using
>>> git-buildpackage?
>>
>> Yes.
>
>Ok, that's reassuring. I'll have a look at the packaging, since I'm
>already on alioth.
>
>But since DPMT is CC-ed (I normally follow via gmane), I take the
>occasion to say that I _really_ _REALLY_ wished the recommendation on
>git-dpm to be reconsidered, or at least relaxed.
>
>For a newcomer, git-dpm is overkill and underdocumented.
>>From an outsider, making a Debian package already looks daunting.
>git-dpm does not help.
>
>On the other hand, git-buildpackage is a relatively smooth progression
>from quilt, and it does provide some added convenience.

Conveniently, we already decided to switch:

https://wiki.debian.org/Python/GitPackagingPQ

Scott K

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

#9795 — Re: git-dpm (was Re: Bug#729956: Forwarded upstream)

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

On 2017-09-07 08:42, Scott Kitterman wrote:

> Conveniently, we already decided to switch:
> 
> https://wiki.debian.org/Python/GitPackagingPQ

Worth noting, while there are some big gotchas with git-dpm, there are
also some big gotchas with GPB PQ. GPB PQ isn't a magical solution that
will solve all our problems. e.g. forgetting to import the PQ (if not
already done) *before* updating to a new upstream version. Or forgetting
to import the PQ after a git pull makes modifications to the upstream
patch files. 

In general, however, when something does go badly wrong I think it will
be a lot easier to diagnose, understand, and fix with GPB PQ then with
git-dpm. git-dpm can get very messy very quickly, particularly if you
forget to pull before making changes (personally I make this mistake too
frequently) or update to a new upstream version without using the
correct git-dpm workflow - I have seen both of these situations happen.

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

#9804 — Re: git-dpm (was Re: Bug#729956: Forwarded upstream)

On Thu, Sep 07 2017, Brian May wrote:
> In general, however, when something does go badly wrong I think it will be a
> lot easier to diagnose, understand, and fix with GPB PQ then with git-dpm.
> git-dpm can get very messy very quickly, particularly if you forget to pull
> before making changes (personally I make this mistake too frequently) or update
> to a new upstream version without using the correct git-dpm workflow - I have
> seen both of these situations happen.

I concur. gbp is not without issues, but as you said, gbp is easier to
reason about and fix.

I don't use gbp daily. In fact, I maintain or edit existing packages not
as frequently as I would like, often having to re-read the documentation
along the way.

The fact that gbp is better documented is a big plus, even if everything
else would be equal. Simplicity goes a long way for cooperative
maintenance. I'm relieved gbp is now the recommended choice.

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

#9796 — Re: git-dpm (was Re: Bug#729956: Forwarded upstream)

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

On 2017-09-07 08:42, Scott Kitterman wrote:

> Conveniently, we already decided to switch:
> 
> https://wiki.debian.org/Python/GitPackagingPQ

It was annoying me that these instructions were missing the last steps
on how to switch the default branch to debian/master and delete the old
branch. 

These steps are very important to: 

(a) prevent confusion on which branch to use. 
(b) prevent confusion on qa.debian.org, which uses the default branch to
check that the git version. 

=== cut === 

ssh git.debian.org
cd "/git/python-modules/packages/$1.git"
git symbolic-ref HEAD refs/heads/debian/master
exit

cd "$TMP"
git push origin :master

=== cut ===

I also have a script to automate the entire conversion, and assuming the
git repository is up-to-date and nobody is withholding pushes, it seems
to work well.  

/srv/home/users/bam/convert on git.debian.org

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

#9801 — Re: git-dpm (was Re: Bug#729956: Forwarded upstream)

On Thursday, September 07, 2017 09:28:11 AM Brian May wrote:
> On 2017-09-07 08:42, Scott Kitterman wrote:
> > Conveniently, we already decided to switch:
> > 
> > https://wiki.debian.org/Python/GitPackagingPQ
> 
> It was annoying me that these instructions were missing the last steps
> on how to switch the default branch to debian/master and delete the old
> branch.
> 
> These steps are very important to:
> 
> (a) prevent confusion on which branch to use.
> (b) prevent confusion on qa.debian.org, which uses the default branch to
> check that the git version.
> 
> === cut ===
> 
> ssh git.debian.org
> cd "/git/python-modules/packages/$1.git"
> git symbolic-ref HEAD refs/heads/debian/master
> exit
> 
> cd "$TMP"
> git push origin :master
> 
> === cut ===
> 
> I also have a script to automate the entire conversion, and assuming the
> git repository is up-to-date and nobody is withholding pushes, it seems
> to work well.
> 
> /srv/home/users/bam/convert on git.debian.org

I know this is excessively snarky, but it's the best I can manage late at 
night:

It's a wiki.  The resolution of your annoyance is within your grasp.

Scott K

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

#9802 — Re: git-dpm (was Re: Bug#729956: Forwarded upstream)

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

On 2017-09-07 14:54, Scott Kitterman wrote:

> It's a wiki.  The resolution of your annoyance is within your grasp.

I had already fixed it. Sorry if I didn't make this clear.

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

#9793

> but the build failed (for other reasons).  I'd willing to work on
> this
> but I definitely need help since I'm lacking the needed Python
> knowledge.

Hi,

I saw your debian-python3 branch for statsmodels.

The dependencies added in the package should probably be added as
build-dependencies. and not package dependencies.

I believe python-zmq should be a binary dependency. 

I was trying to build it right now but I'm getting a dependency error.

 libpython2.7-stdlib : Breaks: python-pandas-lib (<= 0.20.3-1) but
0.20.3-1 is to be installed

Should I see if I can get a python3 build working? and who should I
send any progress too?

Diane

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

#9798

On 06.09.2017 23:45, Diane Trout wrote:
> I was trying to build it right now but I'm getting a dependency error.
> 
>  libpython2.7-stdlib : Breaks: python-pandas-lib (<= 0.20.3-1) but
> 0.20.3-1 is to be installed

this is unrelated, and waiting for #874413.

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

#9799

Hi Diane,

On Wed, Sep 06, 2017 at 02:45:14PM -0700, Diane Trout wrote:
> 
> > but the build failed (for other reasons).  I'd willing to work on
> > this
> > but I definitely need help since I'm lacking the needed Python
> > knowledge.
> 
> Hi,
> 
> I saw your debian-python3 branch for statsmodels.
> 
> The dependencies added in the package should probably be added as
> build-dependencies. and not package dependencies.
> 
> I believe python-zmq should be a binary dependency. 

Thanks for the hints.
 
> I was trying to build it right now but I'm getting a dependency error.
> 
>  libpython2.7-stdlib : Breaks: python-pandas-lib (<= 0.20.3-1) but
> 0.20.3-1 is to be installed

I also get an error in the Python 2.7 test suite so I have no idea
where to continue with the Python3 stuff.

> Should I see if I can get a python3 build working? and who should I
> send any progress too?

Keep on commiting on the debian-python3 branch (or fix everything inside
the debian branch - I simply did not want to crash this ...)  Please
just consider me a poor uneducated guy who only intended to inspire the
more skilled ones to pick up an urgent topic. :-P

Kind regards

     Andreas.

-- 
http://fam-tille.de

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

#9800

On Thu, 2017-09-07 at 06:20 +0200, Andreas Tille wrote:
> Hi Diane,
> 
> On Wed, Sep 06, 2017 at 02:45:14PM -0700, Diane Trout wrote:
> > 
> > > but the build failed (for other reasons).  I'd willing to work on
> > > this
> > > but I definitely need help since I'm lacking the needed Python
> > > knowledge.
> > 
> > Hi,
> > 
> > I saw your debian-python3 branch for statsmodels.
> > 
> > The dependencies added in the package should probably be added as
> > build-dependencies. and not package dependencies.
> > 
> > I believe python-zmq should be a binary dependency. 
> 
> Thanks for the hints.
>  
> > I was trying to build it right now but I'm getting a dependency
> > error.
> > 
> >  libpython2.7-stdlib : Breaks: python-pandas-lib (<= 0.20.3-1) but
> > 0.20.3-1 is to be installed
> 
> I also get an error in the Python 2.7 test suite so I have no idea
> where to continue with the Python3 stuff.

Was the test failures you were see 4 instances like whats shown below?

I found a match upstream at:
https://github.com/statsmodels/statsmodels/issues/3401

I've gotten failures with 2.7 and 3.6.

Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in
runTest
    self.test(*self.arg)
  File
"/home/diane/src/debian/statsmodels/.pybuild/pythonX.Y_2.7/build/statsm
odels/tsa/statespace/tests/test_save.py", line 65, in test_varmax
    res.save('test_save_varmax.p')
  File
"/home/diane/src/debian/statsmodels/.pybuild/pythonX.Y_2.7/build/statsm
odels/base/wrapper.py", line 72, in save
    save_pickle(self, fname)
  File
"/home/diane/src/debian/statsmodels/.pybuild/pythonX.Y_2.7/build/statsm
odels/iolib/smpickle.py", line 15, in save_pickle
    cPickle.dump(obj, fout, protocol=-1)
  File "stringsource", line 2, in
statsmodels.tsa.statespace._statespace.zStatespace.__reduce_cython__
TypeError:
self._design,self._initial_state,self._initial_state_cov,self._obs,self
._obs_cov,self._obs_intercept,self._selected_state_cov,self._selection,
self._state_cov,self._state_intercept,self._transition cannot be
converted to a Python object for pickling

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

#9803

Hi Diane,

On Wed, Sep 06, 2017 at 09:35:58PM -0700, Diane Trout wrote:
> > > 
> > >  libpython2.7-stdlib : Breaks: python-pandas-lib (<= 0.20.3-1) but
> > > 0.20.3-1 is to be installed
> > 
> > I also get an error in the Python 2.7 test suite so I have no idea
> > where to continue with the Python3 stuff.
> 
> Was the test failures you were see 4 instances like whats shown below?
> ...

I'm not sure and I was doing it on a box yesterday evening which I can
not access right now.  At least I need to say that what you quotet in
your mail looked somehow different to what I remember from yesterday.

I have added python3-* Build-Depends now in the debian-python3 branch
but I can not build any mire due to the python-pandas versioned breaks
issue. :-(

Kind regards

     Andreas.

-- 
http://fam-tille.de

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

#9805

Hi

I pushed my work to alioth on the branch detrout-python3

I modified the statsmodels build recipe to at least partially use
pybuild, and the documentation build uses python 3 components instead
of python 2.

I skipped the 4 tests that failed for me, that had an upstream bug
report, when a new version comes out those skips need to be removed.

I tried rebasing on Yuri's latest commit but there was conflicts over
which version of ipython to use that I'm to tired to resolve right now.

It builds python 2 and python 3 statsmodels and statsmodels-lib as well
as the documentation. (including the example notebooks)

There was also some changes because there's were new temp files that
dh_auto_clean needed to fix.

I tried to commit changes in logical chunks for easier review.

There's still problems with dependencies in sid, so all my testing was
against my unclean testing laptop.

Someone should probably debdiff the package against a previous build to
see if anything important got lost.

If it looks good we can discuss if I need to rebase, or if you just
want to merge this work, but right now I need to go to sleep.

Diane

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

#9809 — Bug#729956: Python 3 Statsmodels & Pandas

Hi,

Just wanted to give a progress report

I was able to build a python 3 version of statsmodels, however I wasn't
able to build it against the version of pandas in sid because pandas
can't be installed.

python3-pandas: Pandas is not installable
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875723

I tried rebuilding to get around the cython issue, but then I had some
timezone related unit test failures.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875807

Unfortunately upstream's test environments don't replicate it
https://github.com/pandas-dev/pandas/issues/17533

Looks like the tests pass with conda packages but not Debian packages.
I don't know why yet.

Diane

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

#9810 — Bug#729956: Python 3 Statsmodels & Pandas

On Sat, Sep 16 2017, Diane Trout wrote:
> python3-pandas: Pandas is not installable
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875723

I would have expected the rebuild of python packages affected by the
fpectl extension with a transition, but it doesn't seem to be the case?

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874253

More Breaks where added to {python,python3}-stdlib itself, but there are
still packages which didn't rebuild.

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

#9811 — Bug#729956: Python 3 Statsmodels & Pandas

On Sat, 2017-09-16 at 22:59 +0200, Yuri D'Elia wrote:
> On Sat, Sep 16 2017, Diane Trout wrote:
> > python3-pandas: Pandas is not installable
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875723
> 
> I would have expected the rebuild of python packages affected by the
> fpectl extension with a transition, but it doesn't seem to be the
> case?
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874253
> 
> More Breaks where added to {python,python3}-stdlib itself, but there
> are
> still packages which didn't rebuild.

I was assuming it's because there's a cyclic dependency between pandas
and statsmodels (needed for pandas unit tests), and statsmodels was
also broken by the fpectl problem.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875805

My solution was to use build-profiles to flag the test dependency with
!nocheck

(The diff of the control file changes, though I forgot to add python3-
statsmodels.)

I have a few rules changes too, but I need to separate the changes into
different commits.

--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,7 @@ Section: python
 Priority: optional
 Maintainer: NeuroDebian Team <team@neuro.debian.net>
 Uploaders: Yaroslav Halchenko <debian@onerussian.com>, Michael Hanke <
michael.hanke@g
mail.com>
-Build-Depends: debhelper (>= 7.0.50),
+Build-Depends: debhelper (>= 10),
                python-all-dev (>= 2.5),
                python-setuptools,
                cython,
@@ -11,12 +11,11 @@ Build-Depends: debhelper (>= 7.0.50),
                python-scipy,
                python-tz,
                python-tables [!m68k !sh4 !x32],
-               python-sphinx (>= 1.0~),
-               python-nbsphinx,
-               python-nose,
-               python-pytest,
+               python-sphinx (>= 1.0~) <!nodoc>,
+               python-nbsphinx <!nodoc>,
+               python-nose <!nocheck>,
+               python-pytest <!nocheck>,
                python-matplotlib [!hurd-i386],
-               python-tk,
                python-openpyxl, python-xlwt, python-xlrd,
                python-bs4,
                python-html5lib,
@@ -29,11 +28,10 @@ Build-Depends: debhelper (>= 7.0.50),
                python3-numpy (>= 1:1.7~), python3-dateutil,
                python3-scipy,
                python3-tz,
-               python3-sphinx (>= 1.0~),
-               python3-nose,
-               python3-pytest,
+               python3-sphinx (>= 1.0~) <!nodoc>,
+               python3-nose <!nocheck>,
+               python3-pytest <!nocheck>,
                python3-matplotlib [!hurd-i386]| python-matplotlib (<<
1.2.0~) [!hurd-i386],
-               python3-tk,
                python3-bs4,
                python3-six,
                python3-lxml,
@@ -42,15 +40,15 @@ Build-Depends: debhelper (>= 7.0.50),
                xvfb, xauth, xclip,
 Build-Depends-Indep:
  ipython (>= 0.12) | ipython2x | ipython1x,
- python-statsmodels [!arm64 !ppc64el !sparc64 !mips64el !ppc64
!sparc64 !sh4],
+ python-statsmodels [!arm64 !ppc64el !sparc64 !mips64el !ppc64
!sparc64 !sh4] <!nocheck>,

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

#9812 — Bug#729956: Python 3 Statsmodels & Pandas

On Sat, Sep 16 2017, Diane Trout wrote:
> I was assuming it's because there's a cyclic dependency between pandas
> and statsmodels (needed for pandas unit tests), and statsmodels was
> also broken by the fpectl problem.
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875805
>
> My solution was to use build-profiles to flag the test dependency with
> !nocheck

Looking at python3-skimage-lib (which also requires a rebuild), it seems
that the package failed to pass some tests.

Bug #868582 even includes a patch to update to 0.13 [and disables some
test failures].

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

Page 1 of 4  [1] 2 3 4  Next page →

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

csiph-web