Bug 449648 – dev-python/guess-language-0.2.ebuild - Guess the natural language of a text

• Product: Gentoo Linux
• Status: RESOLVED OBSOLETE

[Description daktak 2013-01-01 14:19:32 UTC]

Guess the natural language of a text

http://code.google.com/p/guess-language

Reproducible: Always

[Comment 1 daktak 2013-01-01 14:20:11 UTC]

Created attachment 333936 [details]
guess-language-0.2.ebuild

[Comment 2 Sergey Popov 2013-01-01 19:04:20 UTC]

Adding new homepage(http://code.google.com/p/guess-language/ is an old one) and Python team to CC

[Comment 3 daktak 2013-01-15 23:29:45 UTC]

Created attachment 335758 [details]
guess-language-0.2.ebuild

Add src_test

[Comment 4 Julian Ospald 2013-01-15 23:43:19 UTC]

use distutils-r1, not distutils

[Comment 5 daktak 2013-01-22 00:45:03 UTC]

Created attachment 336412 [details]
guess-language-0.2.ebuild

changed to distutils-r1 and python-r1

[Comment 6 Ian Delaney (RETIRED) 2013-02-07 14:27:34 UTC]

Russell.
Say after me. I am a goose for not telling idella4 he's a goose for getting the two packages and bugs mixed up.

testuser@archtester ~/improvise/dev-python/guess-language $ ebuild  guess-language-0.2.ebuild clean install

 * common: running distutils-r1_python_install_all
>>> Completed installing guess-language-0.2 into /mnt/gen2/TmpDir/portage/dev-python/guess-language-0.2/image/

perfect.

changed to distutils-r1 and python-r1
wrong, ONLY 1, in this case the 1st. distutils-r1 inherits python-r1


testuser@archtester ~/improvise/dev-python/guess-language $ ebuild  guess-language-0.2.ebuild clean  test

>>> Source compiled.
 * python2.6: running distutils-r1_run_phase python_test
.
----------------------------------------------------------------------
Ran 1 test in 0.002s
OK
 * python2.7: running distutils-r1_run_phase python_test
.
----------------------------------------------------------------------
Ran 1 test in 0.003s
OK
......
----------------------------------------------------------------------
Ran 4 tests in 0.425s
OK
..
----------------------------------------------------------------------
Ran 4 tests in 0.505s
OK
.Good. Now because you got them all to work with your code, here's a little 'extra', the test phase how I'd normally do it which has the same result but is more gentooly correct.

python_test() {
        for test in ${MY_PN}/*_test.py; do
#               echo "running test "$test
                ${PYTHON} $test || die "Failed test "$test
        done
}
Notice I commented out the line just informing running this test. It's not required, and if you uncomment it, you'll see how the multiprocessing makes a cam make a word salad of a build log. In the end that line can go.

From my stance this is good to go. And me makes 3 devs to reply. Oh the luxury of choice.

[Comment 7 Patrice Clement 2016-10-14 11:21:18 UTC]

Is it still wanted? Reopen if it is.