Re: pandas -- I think we should drop BE platforms

Yaroslav Halchenko writes: > 2. Please correct me if I am wrong, but I do not think that there > is some flag to say smth like > > Architecture: any [!big-endian] > > so we would need to unlist them explicitly > > Architecture: any [!s390x, !powerpc, !mips] > > (or

Re: pandas -- I think we should drop BE platforms

That is why I cross posted original email to their mailing lists. Pandas builds are lengthy, codebase complex, I do not remember (m)any patches (besides disabling tests) coming up for those architectures, pretty much for every release we ended up filling RM requests for those architectures. I

Re: pandas -- I think we should drop BE platforms

Hi, Le 24/02/2018 à 21:08, Sébastien Villemot a écrit : > No, leave "Architecture: any". Then the builds will fail on those > arches. This is what porters generally prefer, because they have a > clear information about what is wrong with the package on their > arch (and possibly they can act and

Re: pandas -- I think we should drop BE platforms

On Sat, Feb 24, 2018 at 02:47:19PM -0500, Yaroslav Halchenko wrote: > 1. remove all patches which disable tests on big endians (I would have > even patched to remove upstream skips on those archs, so we do not fall > into the trap of missing smth) I agree with that. > 2. Please correct me if I

pandas -- I think we should drop BE platforms

Hi The Team, "Maintaining" pandas builds on big endians (and some others, but let's concentrate on BE for now) was always problematic. Upstream does not support them and I am somewhat tired of pestering them with failures on them. Only once or twice test failures on those platfor

Re: Patch for pandas RC 884294, someone to sponsor?

lsa.debian.org/science-team/pandas/commits/debian Uploaded and tagged. Again thanks a lot - your work is very much apreciated Andreas. -- http://fam-tille.de

Re: Patch for pandas RC 884294, someone to sponsor?

> I'd volunteer to upload once it is pushed. Please ping me after pushing > since there is not commit mailing list and I'm not sure whether the > tracker solution is implemented yet. Done. https://salsa.debian.org/science-team/pandas/commits/debian -- Best,

Re: Patch for pandas RC 884294, someone to sponsor?

Hi Lumin, On Sat, Jan 20, 2018 at 01:42:43PM +, Lumin wrote: > Control: tags -1 +patch > > Pandas FTBFS on amd64 due to test failure: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884294 > I reproduced this FTBFS on my machine (sid/amd64). > > This test failu

Patch for pandas RC 884294, someone to sponsor?

Control: tags -1 +patch Pandas FTBFS on amd64 due to test failure: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884294 I reproduced this FTBFS on my machine (sid/amd64). This test failure was due to a numpy problem. Upstream workaround (bypass) is available: * https://github.com/pandas-dev

Re: Bus error on armhf (Was: Bug#877419: Bug#877700: RM: pandas [arm64 armel armhf mips mips64el mipsel s390x] ...)

lder? Could somebody > > > please have a look? If not the only chance I see is to deactivate armhf > > > for pandas. > > > > pandas is uncompiled on armhf, so this is not a blocker for testing > > migration. > > I can confirm that > > https://

Re: Bus error on armhf (Was: Bug#877419: Bug#877700: RM: pandas [arm64 armel armhf mips mips64el mipsel s390x] ...)

only chance I see is to deactivate armhf > > for pandas. > > pandas is uncompiled on armhf, so this is not a blocker for testing migration. I can confirm that https://packages.debian.org/buster/python-pandas-lib does not list armhf but https://buildd.debian.org/status/package.ph

Re: Bus error on armhf (Was: Bug#877419: Bug#877700: RM: pandas [arm64 armel armhf mips mips64el mipsel s390x] ...)

Hi Steve, On Tue, Oct 24, 2017 at 10:44:53AM -0700, Steve Langasek wrote: > > (https://launchpad.net/ubuntu/+source/pandas/0.19.2-5.1ubuntu4/+build/13337694) > > This is not a problem with the Debian autobuilder. Something is attempting > an unaligned access, which is not po

Re: Bus error on armhf (Was: Bug#877419: Bug#877700: RM: pandas [arm64 armel armhf mips mips64el mipsel s390x] ...)

s now failed with > ... > ../debian/tmp/usr/lib/python2.7/dist-packages/pandas/tests/io/test_pytables.py::TestHDFStore::test_append_all_nans > PASSED > ../debian/tmp/usr/lib/python2.7/dist-packages/pandas/tests/io/test_pytables.py::TestHDFStore::test_append_frame_column_oriented > Bus erro

Re: Bus error on armhf (Was: Bug#877419: Bug#877700: RM: pandas [arm64 armel armhf mips mips64el mipsel s390x] ...)

lder? Could somebody > please have a look? If not the only chance I see is to deactivate armhf > for pandas. pandas is uncompiled on armhf, so this is not a blocker for testing migration. -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.

Bus error on armhf (Was: Bug#877419: Bug#877700: RM: pandas [arm64 armel armhf mips mips64el mipsel s390x] ...)

Hi, I made some progress with excluding some tests on some architectures. The last target I was trying to tackle was s390x which builds now. Not all architectures have finished [1] currently but armhf has now failed with ... ../debian/tmp/usr/lib/python2.7/dist-packages/pandas/tests/io

Re: [Help] Exclusion did not worked (Was: Bug#877419: Bug#877700: RM: pandas [arm64 armel armhf mips mips64el mipsel s390x] ...)

t; > I added the missing 'import nose' to those two occurences where some old > remainings of nose were used to interrupt tests. I'm not pround about > this very naive but hopefully working approach. Its rather a cry for > more competent people to find a better fix than a solution. I'

Re: [Help] Exclusion did not worked (Was: Bug#877419: Bug#877700: RM: pandas [arm64 armel armhf mips mips64el mipsel s390x] ...)

s rather a cry for more competent people to find a better fix than a solution. I'm just doing the work on pandas since nobody else seems to care for the RC bugs which would kick lots of rdepends. Since I'm offline tomorrow, please pretty please could somebody check and try some next iteration to t

Re: [Help] Exclusion did not worked (Was: Bug#877419: Bug#877700: RM: pandas [arm64 armel armhf mips mips64el mipsel s390x] ...)

On 16 Oct 2017, at 11:08, Andreas Tille wrote: > On Sun, Oct 15, 2017 at 08:21:46PM +0100, Rebecca N. Palmer wrote: >>> raise nose.SkipTest("known failure of test_stata on non-little endian") >>> E NameError: name 'nose' is not defined >> >> You need an 'import nose'

Re: [Help] Exclusion did not worked (Was: Bug#877419: Bug#877700: RM: pandas [arm64 armel armhf mips mips64el mipsel s390x] ...)

On Sun, Oct 15, 2017 at 08:21:46PM +0100, Rebecca N. Palmer wrote: > > raise nose.SkipTest("known failure of test_stata on non-little endian") > > E NameError: name 'nose' is not defined > > You need an 'import nose' first, if the test doesn't already have one. If the 'import nose' is

Re: [Help] Exclusion did not worked (Was: Bug#877419: Bug#877700: RM: pandas [arm64 armel armhf mips mips64el mipsel s390x] ...)

p/usr/lib/python2.7/dist-packages/pandas/tests/io/test_stata.py > ../debian/tmp/usr/lib/python2.7/dist-packages/pandas/tests/io/test_stata.py:27: > in > raise nose.SkipTest("known failure of test_stata on non-little endian") > E NameError: name 'nose' is not define

Re: [Help] Exclusion did not worked (Was: Bug#877419: Bug#877700: RM: pandas [arm64 armel armhf mips mips64el mipsel s390x] ...)

raise nose.SkipTest("known failure of test_stata on non-little endian") E NameError: name 'nose' is not defined You need an 'import nose' first, if the test doesn't already have one.

Re: [Help] Exclusion did not worked (Was: Bug#877419: Bug#877700: RM: pandas [arm64 armel armhf mips mips64el mipsel s390x] ...)

Hi, for arm64 the method I uploaded has seemed to work but for mips and s390x it ends up in ... ERRORS ERROR collecting debian/tmp/usr/lib/python2.7/dist-packages/pandas/tests/io/test_stata.py ../debian/tmp/usr/lib

Re: [Help] Exclusion did not worked (Was: Bug#877419: Bug#877700: RM: pandas [arm64 armel armhf mips mips64el mipsel s390x] ...)

ore now pass. (we have got something like that in > datalad now for demarkating tests which fail atm with v6 of git-annex > repo) > > upstream actually already has some tests marked up: > > pandas/tests/indexes/test_interval.py: > @pytest.mark.skipif(compat.is_platform_32bit(

Re: [Help] Exclusion did not worked (Was: Bug#877419: Bug#877700: RM: pandas [arm64 armel armhf mips mips64el mipsel s390x] ...)

o_fail_on_nonx32 see https://docs.pytest.org/en/latest/skipping.html#id1 on how to establish those for now based on skipif . "For now", since ideally there should be an easy way to trigger another behavior -- test which tests known to fail before now pass. (we have got something like that

Re: [Help] Exclusion did not worked (Was: Bug#877419: Bug#877700: RM: pandas [arm64 armel armhf mips mips64el mipsel s390x] ...)

think the proper way would be to login to each single architecture and build there this would not fit into my time frame I'm willing to spent on this task. I treid to approach this by re-using the exclusion mechanism that was used before (but not activated) in the rules file of pandas[1]: diff

[Help] Exclusion did not worked (Was: Bug#877419: Bug#877700: RM: pandas [arm64 armel armhf mips mips64el mipsel s390x] ...)

> way would be to login to each single architecture and build there this > would not fit into my time frame I'm willing to spent on this task. I treid to approach this by re-using the exclusion mechanism that was used before (but not activated) in the rules file of pandas[1]: diff --git a/deb

Pandas packaging moved to Debian Science (Was: Bug#877419: Bug#877700: RM: pandas [arm64 armel armhf mips mips64el mipsel s390x] -- ROM; Some build time tests are failing on specific architectures)

On Fri, Oct 13, 2017 at 01:51:51PM -0400, Yaroslav Halchenko wrote: > > >2. Upload after migrating the package to Debian Science as > > we previously agreed upon. > > do you mean migrating of a Vcs? Pandas is now at https://anonscm.debian.org/git/debian-scienc

Re: Bug#877419: Bug#877700: RM: pandas [arm64 armel armhf mips mips64el mipsel s390x] -- ROM; Some build time tests are failing on specific architectures

ere anybody who is no happy about this? > > sorry to be the pain, I am ... And first of all -- thanks for taking > care about pandas! No need to sorry. > I would disagree on the complete disabling of the tests. Selective > annotation of failed tests at least allows maintaine

Re: Bug#877419: Bug#877700: RM: pandas [arm64 armel armhf mips mips64el mipsel s390x] -- ROM; Some build time tests are failing on specific architectures

On Fri, 13 Oct 2017, Andreas Tille wrote: >1. proceed as I suggested here: > https://lists.debian.org/debian-science/2017/10/msg1.html >... > Is there anybody who is no happy about this? sorry to be the pain, I am ... And first of all -- thanks for taking care abou

Re: Bug#877700: RM: pandas [arm64 armel armhf mips mips64el mipsel s390x] -- ROM; Some build time tests are failing on specific architectures

On Fri, Oct 13, 2017 at 06:10:58PM +0100, James Clarke wrote: > On 13 Oct 2017, at 18:06, Andreas Tille wrote: > > > > OK folks, if nobody insists I'll do the following > > > > 1. proceed as I suggested here: > >

Re: Bug#877700: RM: pandas [arm64 armel armhf mips mips64el mipsel s390x] -- ROM; Some build time tests are failing on specific architectures

3, 2017 at 07:00:04PM +0300, Adrian Bunk wrote: >> On Wed, Oct 04, 2017 at 05:23:58PM +0200, Andreas Tille wrote: >>> Package: ftp.debian.org >>> Severity: normal >>> >>> Hi ftpmasters, >>> >>> as discussed in detail on Debian Science lis

Re: Bug#877700: RM: pandas [arm64 armel armhf mips mips64el mipsel s390x] -- ROM; Some build time tests are failing on specific architectures

on Debian Science list[1] please remove pandas > > for the said architectures to enable lowering severity of bug #877419 > > and let the package migrate to testing at least for the working > > architectures. > > > > Thanks a lot for your ftpmaster work > > >

Re: skimage (was: Re: Bug#729956: Python 3 Statsmodels & Pandas)

On Tue, 10 Oct 2017, Yuri D'Elia wrote: > On Sat, Sep 16 2017, Yuri D'Elia wrote: > > 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

Re: skimage (was: Re: Bug#729956: Python 3 Statsmodels & Pandas)

On Tue, Oct 10, 2017 at 10:32:29PM +0200, Yuri D'Elia wrote: > On Sat, Sep 16 2017, Yuri D'Elia wrote: > > 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

skimage (was: Re: Bug#729956: Python 3 Statsmodels & Pandas)

On Sat, Sep 16 2017, Yuri D'Elia wrote: > 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]. Has anyone had a chance to look at skimage

Re: How to deal with pandas

Hi, my message seems to got lost; re-posting: Sébastien Villemot <sebast...@debian.org> writes: > On Wed, Oct 04, 2017 at 03:43:00PM +0200, Anton Gladky wrote: >> one more > option is to drop pandas on those archs (filing RM bug) >> and fill the list of supported archs

pandas arm & mips FTBFS #877754

Hi, It's pretty difficult to run just one pandas unittest. I managed to extract a couple examples from the build logs and replicate the failures on a arm64 porterbox. Debian Bug is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877754 Forwarded to https://github.com/pandas-dev/pandas/issues

Re: How to deal with pandas

On Wed, Oct 04, 2017 at 04:49:58PM +0200, Sébastien Villemot wrote: > > Thanks for checking. So would you volunteer to file the RM bug (or ask > > me to do so which would be fine as well - just to make sure we will not > > file two or more bugs at the same time). > > Please do so. Thanks. Done

Re: How to deal with pandas

Sébastien Villemot <sebast...@debian.org> writes: > On Wed, Oct 04, 2017 at 03:43:00PM +0200, Anton Gladky wrote: > >> one more option is to drop pandas on those archs (filing >> RM bug) and fill the list of supported archs explicitly >> in d/control. > > If

Bug#877700: RM: pandas [arm64 armel armhf mips mips64el mipsel s390x] -- ROM; Some build time tests are failing on specific architectures

Package: ftp.debian.org Severity: normal Hi ftpmasters, as discussed in detail on Debian Science list[1] please remove pandas for the said architectures to enable lowering severity of bug #877419 and let the package migrate to testing at least for the working architectures. Thanks a lot

Re: How to deal with pandas

f it is a > > bit > > sad to see the package go on so many archs, also knowing that it never > > compiled > > on armhf): > > > > sebastien@coccia:~$ dak rm -A -b -a arm64,armel,mips,mip

Re: How to deal with pandas

> compiled > on armhf): > > sebastien@coccia:~$ dak rm -A -b -a arm64,armel,mips,mips64el,mipsel,s390x -p > -R -n python-pandas-lib python3-pandas-lib > > Will remove the following pack

Re: How to deal with pandas

> > > > > > one more option is to drop pandas on those archs (filing > > > > RM bug) and fill the list of supported archs explicitly > > > > in d/control. > > > > > > If the pandas binaries are known broken on those archs, then it is the

Re: How to deal with pandas

On Wed, Oct 04, 2017 at 04:00:23PM +0200, Sébastien Villemot wrote: > On Wed, Oct 04, 2017 at 03:52:56PM +0200, Sébastien Villemot wrote: > > On Wed, Oct 04, 2017 at 03:43:00PM +0200, Anton Gladky wrote: > > > > > one more option is to drop pandas on those archs (filin

Re: How to deal with pandas

On Wed, Oct 04, 2017 at 03:52:56PM +0200, Sébastien Villemot wrote: > On Wed, Oct 04, 2017 at 03:43:00PM +0200, Anton Gladky wrote: > > > one more option is to drop pandas on those archs (filing > > RM bug) and fill the list of supported archs explicitly > > in d/con

Re: How to deal with pandas

itectures that are >> known to fail (see attached patch, NOT TESTED, please review) >> 2. Drop severity of the bug from serious to important >> 3. Fix bug #877419 later but let pandas and its dependencies >> (statsmodels and lots of others) migrate to testing >

Re: How to deal with pandas

On Wed, Oct 04, 2017 at 03:43:00PM +0200, Anton Gladky wrote: > one more option is to drop pandas on those archs (filing > RM bug) and fill the list of supported archs explicitly > in d/control. If the pandas binaries are known broken on those archs, then it is the only acceptable so

Re: How to deal with pandas

Hi Andreas, one more option is to drop pandas on those archs (filing RM bug) and fill the list of supported archs explicitly in d/control. Anton 2017-10-04 15:13 GMT+02:00 Andreas Tille <andr...@an3as.eu>: > Hi, > > to deal with #877419 I'd suggest the following approach: &

How to deal with pandas

Hi, to deal with #877419 I'd suggest the following approach: 1. Ignore test suite errors on those architectures that are known to fail (see attached patch, NOT TESTED, please review) 2. Drop severity of the bug from serious to important 3. Fix bug #877419 later but let pandas

Re: Python 3 Statsmodels & Pandas

On 30/09/17 16:50, Diane Trout wrote: I am curious if Rebecca is using pandas on a non-intel architecture though (was wondering how she noticed pandas hadn't built) No - I found this email thread and checked https://buildd.debian.org/status/package.php?p=pandas

Re: Python 3 Statsmodels & Pandas

x in B-D-Indep > is > probably the easiest solution. Also you can try not relying on --with > at all and manually call dh_sphinxdoc when the build is arch-indep. > It took me two tries, but statsmodels 0.8.0-6 builds everywhere pandas builds now. I am curious if Rebecca is using

Re: Python 3 Statsmodels & Pandas

Hi Diane, On Fri, Sep 29, 2017 at 03:55:13PM -0700, Diane Trout wrote: > Oops. > > I thought that it wouldn't try using sphinx when not building doc > packages. But apparently being listed in "dh --with" counts as being > used. Yes, because dh tries to open Sequece/sphinxdoc.pm which is provided

Re: Python 3 Statsmodels & Pandas

On 29/09/17 23:55, Diane Trout wrote: On Fri, 2017-09-29 at 22:05 +0100, Rebecca N. Palmer wrote: statsmodels passed NEW...and FTBFS with dh: unable to load addon sphinxdoc: Can't locate Debian/Debhelper/Sequence/sphinxdoc.pm in @INC That file is in the sphinx-common package, which suggests

Re: Python 3 Statsmodels & Pandas

On 29/09/17 23:55, Diane Trout wrote: I wonder if it's better to filter sphinxdoc out of the dh line, install sphinx-common, or just always install python3-sphinx? For local testing of this, use pbuilder --debbuildopts -B Given earlier messages that we want this working ASAP, always

Re: Python 3 Statsmodels & Pandas

o filter sphinxdoc out of the dh line, install sphinx-common, or just always install python3-sphinx? I have some ideas of what to do, I should be able to fix this soon. > > Meanwhile, pandas FTBFS with several failing tests (all involving > datetime) on arm*/mips*el and a broken attempt to s

Re: Python 3 Statsmodels & Pandas

-Indep. Meanwhile, pandas FTBFS with several failing tests (all involving datetime) on arm*/mips*el and a broken attempt to skip a test (trying to raise nose.SkipTest without importing nose) on mips/s390x.

Re: Python 3 Statsmodels & Pandas

Hi again, On Wed, Sep 27, 2017 at 10:05:15AM +0200, Andreas Tille wrote: > > I added the readme to README.source with a bit of explanatory text. > > > > all changes are pushed. > > Seems the updated README.source escaped your push. ;-) I think I've restored it from the link you posted below

Re: Python 3 Statsmodels & Pandas

Dear Diane, On Wed, Sep 27, 2017 at 12:20:13AM -0700, Diane Trout wrote: > > > > I think there is no "right" place to do it - but ftpmaster is used > > to read README.source in these cases. So why not using it? > > > > I added the readme to README.source with a bit of explanatory text. > >

Re: Python 3 Statsmodels & Pandas

On Wed, 2017-09-27 at 08:34 +0200, Andreas Tille wrote: > > > > > https://ghic.org/~diane/debian/statsmodels.datasets.README.txt > > I think regarding formatting and context its perfectly fine. > > > Does it go in README.source? or in upstream/metadata? or something > > else? > > I think

Re: Python 3 Statsmodels & Pandas

Dear Diane, On Tue, Sep 26, 2017 at 10:47:21PM -0700, Diane Trout wrote: > > > Since it is accepted for the R packages and the data are refering > > to R data I do not see any reason why this should not be accepted. > > I traced back from Rdatasets to the original R packages. > > Every one of

Re: Python 3 Statsmodels & Pandas

Dear Diane, On Tue, Sep 26, 2017 at 02:49:12PM -0700, Diane Trout wrote: > > > While I have not tried to build the current status I wonder what you > > think about #873512. I'm perfectly fine with your solution to > > exclude > > some tests - I just wanted to give a hint that there is a

Re: Python 3 Statsmodels & Pandas

> Since it is accepted for the R packages and the data are refering > to R data I do not see any reason why this should not be accepted. I traced back from Rdatasets to the original R packages. Every one of the packages are licensed as some combination of GPL-2 and GPL-3 However it's likely

Re: Python 3 Statsmodels & Pandas

> While I have not tried to build the current status I wonder what you > think about #873512. I'm perfectly fine with your solution to > exclude > some tests - I just wanted to give a hint that there is a potential > upstream patch. I think I looked at the upstream commits that fixed it,

Re: Python 3 Statsmodels & Pandas

Hi Diane, On Tue, Sep 26, 2017 at 11:36:17AM -0700, Diane Trout wrote: > > BTW, I'd love if you would merge your work to master branch. I'm a > > bit > > confused by the amount of branches and lost track which one to look > > at. > > I verified which was which and deleted the obsolete branch. >

Re: Python 3 Statsmodels & Pandas

Thanks for digging into this and sorry I have missed that. I typically add export http*_proxy to prevent any network interactions but I guess didn't get that far with statsmodels. FWIW, for dipy package I now ask upstream to provide me e.g. dipy_0.12.0.orig-doc-examples.tar.gz where there

Re: Python 3 Statsmodels & Pandas

> > Below is what I've found so far, (before getting tired of licensing > > issues) > > > > Any thoughts about how to handle this? > > I wonder how this was dealt with before? If that much data sets were > needed to build the docs, how did the doc generation process worked > before? Perhaps

Re: Python 3 Statsmodels & Pandas

On Mon, Sep 25, 2017 at 09:36:43PM -0700, Diane Trout wrote: > > > * Some of the doc pages call get_rdataset, and there's no network > > > access in the builder so those calls fail. (ugliest error) > > > > Can you pre-fetch the data and provide it in debian/datasets? > > I made the changes and

Re: Python 3 Statsmodels & Pandas

On Mon, 2017-09-25 at 09:44 +0200, Andreas Tille wrote: > Hi Diane, > > On Sun, Sep 24, 2017 at 11:45:43PM -0700, Diane Trout wrote: > > The remaining issues are: > > > > * Some of the doc pages call get_rdataset, and there's no network > > access in the builder so those calls fail. (ugliest

Re: Python 3 Statsmodels & Pandas

Hi Diane, On Mon, Sep 25, 2017 at 10:38:00AM -0700, Diane Trout wrote: > > I'm planning on ignoring it for now. Sounds sensible. Thanks a lot for your work on this Andreas. -- http://fam-tille.de

Re: Python 3 Statsmodels & Pandas

On Mon, 2017-09-25 at 09:44 +0200, Andreas Tille wrote: > > > * Some of the doc pages call get_rdataset, and there's no network > > access in the builder so those calls fail. (ugliest error) > > Can you pre-fetch the data and provide it in debian/datasets? Looks like it'll take a bit of

Re: Python 3 Statsmodels & Pandas

> > > I made larger changes to statsmodels, by using pybuild instead of the > > > previous multiple targets in debian/rules. > > you can simplify it even further by using pybuild's --ext-dest-dir: > > (I didn't test as this branch FTBFS for me) > how recent is that feature? it's available since

Re: Python 3 Statsmodels & Pandas

Hi Diane, On Sun, Sep 24, 2017 at 11:45:43PM -0700, Diane Trout wrote: > The remaining issues are: > > * Some of the doc pages call get_rdataset, and there's no network > access in the builder so those calls fail. (ugliest error) Can you pre-fetch the data and provide it in debian/datasets? >

Re: Python 3 Statsmodels & Pandas

On Sun, Sep 24, 2017 at 04:16:48PM -0700, Diane Trout wrote: > If the jquery.js file is deleted something later errors out. My guess is > it's listed in one of the .install files but I haven't looked yet That's what I understood - that's why it should be safe to remove it from the installed dir

Re: Python 3 Statsmodels & Pandas

On Sun, 2017-09-24 at 11:24 -0700, Diane Trout wrote: > Status with statsmodels almost done > > Trying to deal with jquery. > > leaving command > > -rm ./build/html/_static/jquery.js > > causes a build failure now. > leaving it in causes a lintain privacy error. I found the problem, I

Re: Python 3 Statsmodels & Pandas

On Sun, 24 Sep 2017, Andreas Tille wrote: > Hi Yaroslav, > On Sat, Sep 23, 2017 at 10:00:35AM -0400, Yaroslav Halchenko wrote: > > > I would prefer to move pandas to Debian Science or Debian Python. I > > > fail to see the specific use in NeuroDebian field. > &

Re: Python 3 Statsmodels & Pandas

On Sun, 24 Sep 2017, Andreas Tille wrote: > On Sun, Sep 24, 2017 at 11:24:10AM -0700, Diane Trout wrote: > > Status with statsmodels almost done > > Trying to deal with jquery. > > leaving command > > -rm ./build/html/_static/jquery.js > > causes a build failure now. > Without checking

Re: Python 3 Statsmodels & Pandas

On Sun, Sep 24, 2017 at 11:24:10AM -0700, Diane Trout wrote: > Status with statsmodels almost done > > Trying to deal with jquery. > > leaving command > > -rm ./build/html/_static/jquery.js > > causes a build failure now. Without checking the source: I'm usually doing something like

Re: Python 3 Statsmodels & Pandas

Status with statsmodels almost done Trying to deal with jquery. leaving command -rm ./build/html/_static/jquery.js causes a build failure now. leaving it in causes a lintain privacy error. there's also lintain warnings about a missing hardening flag, and no doc-base registration. At

Re: Python 3 Statsmodels & Pandas

Hi Yaroslav, On Sat, Sep 23, 2017 at 10:00:35AM -0400, Yaroslav Halchenko wrote: > > > I would prefer to move pandas to Debian Science or Debian Python. I > > fail to see the specific use in NeuroDebian field. > > I ould repeat that I don't mind having it moved under

Re: Python 3 Statsmodels & Pandas

On Fri, 22 Sep 2017, Andreas Tille wrote: > > diff -Nru pandas-0.20.3/debian/changelog pandas-0.20.3/debian/changelog > > --- pandas-0.20.3/debian/changelog 2017-07-10 20:00:59.0 -0400 > > +++ pandas-0.20.3/debian/changelog 2017-09-21 16:11:29.0 -0400

Re: Python 3 Statsmodels & Pandas

On Fri, 22 Sep 2017, Piotr Ożarowski wrote: > [Diane Trout, 2017-09-21] > > I made larger changes to statsmodels, by using pybuild instead of the > > previous multiple targets in debian/rules. > you can simplify it even further by using pybuild's --ext-dest-dir: > (I didn't test as this branch

Re: Python 3 Statsmodels & Pandas

On 22/09/17 20:32, Diane Trout wrote: On Fri, 2017-09-22 at 10:57 +0200, Piotr Ożarowski wrote: [Diane Trout, 2017-09-21] I made larger changes to statsmodels, by using pybuild instead of the previous multiple targets in debian/rules. you can simplify it even further by using pybuild's

Re: Python 3 Statsmodels & Pandas

On Fri, 2017-09-22 at 10:57 +0200, Piotr Ożarowski wrote: > [Diane Trout, 2017-09-21] > > I made larger changes to statsmodels, by using pybuild instead of > > the > > previous multiple targets in debian/rules. > > you can simplify it even further by using pybuild's --ext-dest-dir: > (I didn't

Re: Python 3 Statsmodels & Pandas

[Diane Trout, 2017-09-21] > I made larger changes to statsmodels, by using pybuild instead of the > previous multiple targets in debian/rules. you can simplify it even further by using pybuild's --ext-dest-dir: (I didn't test as this branch FTBFS for me) diff --git a/debian/rules b/debian/rules

Re: Python 3 Statsmodels & Pandas

the work. > > > I was btw also trying to build with the patch you shared yesterday > > > Once I have all the changes for pandas would you like me to put them on > > a branch on alioth? Or should I send them via format-patch somewhere? > > I could work with either.

Re: Python 3 Statsmodels & Pandas

for doc building. After more testing I'll try posting them. But it probably wont be until tomorrow. diff -Nru pandas-0.20.3/debian/changelog pandas- > 0.20.3/debian/changelog > --- pandas-0.20.3/debian/changelog 2017-07-10 20:00:59.0 > -0400 > +++ pandas-0.20.3/debi

Re: Python 3 Statsmodels & Pandas

On Thu, 21 Sep 2017, Diane Trout wrote: > On Thu, 2017-09-21 at 17:56 -0400, Yaroslav Halchenko wrote: > > If you could allow to review would be great. > > Thanks for all the work. > > I was btw also trying to build with the patch you shared yesterday > Once I have al

Re: Python 3 Statsmodels & Pandas

some working spatstats to continue with other >> packages. >> > >Status: > >[X] Pandas builds with nocheck, nodoc >[X] Statsmodels builds with Python 3 using above pandas >[X] Pandas tests pass with statsmodels for Python 2 & 3 installed. >[ ] Pandas builds docs

Re: Python 3 Statsmodels & Pandas

On Thu, 2017-09-21 at 17:56 -0400, Yaroslav Halchenko wrote: > If you could allow to review would be great. > Thanks for all the work. > I was btw also trying to build with the patch you shared yesterday Once I have all the changes for pandas would you like me to put them on a branch

Re: Python 3 Statsmodels & Pandas

ular depenendecies). > > We somehow need to get some working spatstats to continue with other > packages. > Status: [X] Pandas builds with nocheck, nodoc [X] Statsmodels builds with Python 3 using above pandas [X] Pandas tests pass with statsmodels for Python 2 & 3 installed. [ ] P

Re: Python 3 Statsmodels & Pandas

now, this situation with pandas and statsmodels is slowing work on other scientific packages down significantly. Cheers, Ghis

Re: Python 3 Statsmodels & Pandas

Hi, On Mon, Sep 18, 2017 at 05:48:48PM +1000, Stuart Prescott wrote: > On Sunday, 17 September 2017 22:14:18 AEST Diane Trout wrote: > > I just did it that way because it was the least disruptive change I > > could make that would let me build and test the package. > > Sure, that's entirely

Re: Python 3 Statsmodels & Pandas

Hi Diane, On Sunday, 17 September 2017 22:14:18 AEST Diane Trout wrote: > I just did it that way because it was the least disruptive change I > could make that would let me build and test the package. Sure, that's entirely sensible. > In my experience I'm much more likely to to notice a build

Re: Python 3 Statsmodels & Pandas

Hi Diane & other science+python people, Thanks for spending time on pandas and statsmodels. They are two very valuable but very painful packages to work on. I've not looked at pandas and statsmodels packages carefully beyond "why hasn't pandas migrated this time!?"

Re: Python 3 Statsmodels & Pandas

On 16.09.2017 22:59, 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 ext

Re: 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

Re: 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 t

Re: 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?

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

Re: Help needed for pandas bug: Could anybody verify the suspicion that tzdata might have some influence?

s that it (package) built fine > > https://buildd.debian.org/status/logs.php?pkg=pandas=0.19.2-5=amd64 > Rebecca N. Palmer has kindly provided a patch that fits the discussion > inside the bug (thanks a lot Rebecca). It worked for me and thus I > uploaded (having a pristine-tar branch

<    1   2   3   >