bob issueshttps://gitlab.idiap.ch/groups/bob/-/issues2019-02-20T13:58:52Zhttps://gitlab.idiap.ch/bob/bob.devtools/-/issues/5Out-of-source test-only runs are bound to fail2019-02-20T13:58:52ZAndré AnjosOut-of-source test-only runs are bound to failThis is not an issue per see, but more like a feature request. With the current test strategy implemented in bob.admin#100, conda packages are supposed to contain all material that is required to test them.
This is not true for the `do...This is not an issue per see, but more like a feature request. With the current test strategy implemented in bob.admin#100, conda packages are supposed to contain all material that is required to test them.
This is not true for the `doc` directory of source packages, therefore testing any package inside `bob` out of its source present is bound to fail.
My impression is that this could be mitigated if we were not "building" the documentation during "test" time, but rather during build time.
It would be nice to understand why that is not the case, @amohammadi.André AnjosAndré Anjoshttps://gitlab.idiap.ch/bob/bob.ip.pytorch_extractor/-/issues/4Simplify the MultiNetPatchExtractor and MLPAlgorithm2019-02-18T13:37:38ZOlegs NIKISINSSimplify the MultiNetPatchExtractor and MLPAlgorithmHey @heusch ,
As you pointed out these two classes are controlled by configs:
https://gitlab.idiap.ch/bob/bob.ip.pytorch_extractor/blob/master/bob/ip/pytorch_extractor/MultiNetPatchExtractor.py
https://gitlab.idiap.ch/bob/bob.ip.pytor...Hey @heusch ,
As you pointed out these two classes are controlled by configs:
https://gitlab.idiap.ch/bob/bob.ip.pytorch_extractor/blob/master/bob/ip/pytorch_extractor/MultiNetPatchExtractor.py
https://gitlab.idiap.ch/bob/bob.ip.pytorch_extractor/blob/master/bob/ip/pytorch_extractor/MLPAlgorithm.py
Completely agree with you, this is not convenient resulting to have "configs in the configs".
Will refactor that tomorrow, removing the need for controlling configs in above files. Please let me know if you have any comments on that. Thanks!Olegs NIKISINSOlegs NIKISINShttps://gitlab.idiap.ch/bob/bob.ip.pytorch_extractor/-/issues/5MLPAlgorithm should be implemented as a bob.pad.base.algorithm2019-02-15T15:47:20ZGuillaume HEUSCHMLPAlgorithm should be implemented as a bob.pad.base.algorithmIt would be nice to implement the MLP as a `bob.pad.base.algorithm` child, this way, it could be used seamlessly with `spoof.py` and hence simplify the whole pipeline !It would be nice to implement the MLP as a `bob.pad.base.algorithm` child, this way, it could be used seamlessly with `spoof.py` and hence simplify the whole pipeline !https://gitlab.idiap.ch/bob/bob.devtools/-/issues/14caching is not working on macos?2019-02-15T05:54:47ZAmir MOHAMMADIcaching is not working on macos?I saw the cache being created in https://gitlab.idiap.ch/bob/bob.ip.dlib/-/jobs/157412
but I can't see it being extracted in https://gitlab.idiap.ch/bob/bob.ip.dlib/-/jobs/157414
I can see the cache working in linux: https://gitlab.idia...I saw the cache being created in https://gitlab.idiap.ch/bob/bob.ip.dlib/-/jobs/157412
but I can't see it being extracted in https://gitlab.idiap.ch/bob/bob.ip.dlib/-/jobs/157414
I can see the cache working in linux: https://gitlab.idiap.ch/bob/bob.ip.dlib/-/jobs/157413
Am I missing something?André AnjosAndré Anjoshttps://gitlab.idiap.ch/bob/bob/-/issues/144Automatic VM generation after a release2019-02-13T14:33:28ZAndré AnjosAutomatic VM generation after a release*Created by: anjos*
> This request was migrated from #104
The idea is to be able to generated, in a completely unattended manner, a VM everytime we have a new release for Bob and that this VM can be used as a reference for other peop...*Created by: anjos*
> This request was migrated from #104
The idea is to be able to generated, in a completely unattended manner, a VM everytime we have a new release for Bob and that this VM can be used as a reference for other people.
One of the options is to use TinyCore - this distribution is blazing fast and boots quickly:
> To generate a package for the TinyCore distribution:
> http://distro.ibiblio.org/tinycorelinux/downloads.html In particular, it would be nice to
> automatize the process of generating a VirtualBox VDI with bob install, potentially
> based on the tiny linux distribution TinyCore.https://gitlab.idiap.ch/bob/bob/-/issues/117"hides overloaded virtual function [-Woverloaded-virtual]" warnings with llvm...2019-02-13T14:33:28ZAndré Anjos"hides overloaded virtual function [-Woverloaded-virtual]" warnings with llvm/clang*Created by: laurentes*
I've noticed the following warnings when we use the llvm/clang compiler (only on OS X):
```
/Users/buildbot/work/buildbot/macosx-10.8-x86_64-incremental+master/build/include/bob/trainer/IVectorTrainer.h:122:10:...*Created by: laurentes*
I've noticed the following warnings when we use the llvm/clang compiler (only on OS X):
```
/Users/buildbot/work/buildbot/macosx-10.8-x86_64-incremental+master/build/include/bob/trainer/IVectorTrainer.h:122:10: warning: 'bob::trainer::IVectorTrainer::is_similar_to' hides overloaded virtual function [-Woverloaded-virtual]
1 warning generated.
/Users/buildbot/work/buildbot/macosx-10.8-x86_64-incremental+master/build/include/bob/trainer/IVectorTrainer.h:122:10: warning: 'bob::trainer::IVectorTrainer::is_similar_to' hides overloaded virtual function [-Woverloaded-virtual]
1 warning generated.
```
cf. [here](https://www.idiap.ch/software/bob/buildbot/builders/0-macosx-10.8-x86_64-incremental%2Bmaster/builds/465/steps/compile/logs/warnings%20%2819%29)
I don't understand why this is occuring. Does anyone have a clue? The recipe to get rid of them is to change the inline definition in the templated class EMTrainer
```c++
virtual bool is_similar_to(const EMTrainer& b, const double r_epsilon=1e-5, const double a_epsilon=1e-8) const
{
return m_compute_likelihood == b.m_compute_likelihood &&
bob::core::isClose(m_convergence_threshold, b.m_convergence_threshold, r_epsilon, a_epsilon) &&
m_max_iterations == b.m_max_iterations;
}
```
into a single declaration within the EMTrainer class definition
```c++
bool is_similar_to(const IVectorTrainer& b, const double r_epsilon=1e-5, const double a_epsilon=1e-8) const;
```
and a definition of this method outside the class as follows
```c++
template<class T_machine, class T_sampler>
bool bob::trainer::EMTrainer<T_machine,T_sampler>::is_similar_to(const bob::trainer::EMTrainer<T_machine,T_sampler>& b,
const double r_epsilon, const double a_epsilon) const
{
return m_compute_likelihood == b.m_compute_likelihood &&
bob::core::isClose(m_convergence_threshold, b.m_convergence_threshold, r_epsilon, a_epsilon) &&
m_max_iterations == b.m_max_iterations;
}
```
This only happens for is_similar_to method and not for operator==(), which means that the default/optional arguments might be the cause of the problem.v1.2https://gitlab.idiap.ch/bob/bob/-/issues/104Wishes for the next major release (1.2.0)2019-02-13T14:33:28ZAndré AnjosWishes for the next major release (1.2.0)*Created by: laurentes*
I've decided to create a thread to help us to converge towards a better Bob for the next major release. I doubt we will have the time to deal with everything shortly, but there will be at least a trace of it. Fee...*Created by: laurentes*
I've decided to create a thread to help us to converge towards a better Bob for the next major release. I doubt we will have the time to deal with everything shortly, but there will be at least a trace of it. Feel free to update this thread with your thoughts/wishes.
## To consolidate what is already there
1. The user guide is already fairly good. I would not say the same about the documentation of the python bindings that show up when using the `help()` function of python. For many functions/classes, this documentation is very limited and unhelpful.
2. The library is becoming larger. We should have stricter rule when defining class methods that refers to the same concept. For instance, very often, we have a variable related to the input/feature dimensionality. Depending on the class, it might be obtained using a 'getDimD()', 'inputDims()', or whatsoever. I think this is very annoying from a user perspective. Same for the API of the trainers.
3. For many functions, we have two different kinds of python bindings: one kind which follows the C++ API (e.g. void f(const BA& input, BA& output)), and one which is more
'pythonic' (e.g. BA f(const BA& input)). These two bindings often share the same python function name. I don't think this is a good strategy, as these sometimes leads to impossible cases when the C++ API has many overloaded functions. I think the function name should reflect this difference. OpenCV strategy was roughly to used two different namespaces (cv for the C like functions, and cv2 for the pythonic one). We could do something slightly different such as appending the function name with something like '_c' or '_cc' to clearly highlight this fact.
4. ~~As previously discussed, the LBP code could be refactored in a single more generic but parametrized class.~~ (Already done by Manuel)
5. Learning from our previous experiences, I would be in favour of making mandatory a version number to any class that provides a 'save_to_hdf5' method.
6. ~~Add a tutorial for the Audio Processing module~~ (Already done by Elie)
7. Provide is_similar_to(const Object& b, const double epsilon=1e-8) functions for all C++ classes that have double members. The default "==" and "!=" operators are largely useless when we want to provide code that runs on several platforms (i.e., 32 and 64 bit machines).
8. ~~Whenever a C++ class uses some random initialization, make sure that you can seed this randomness.~~ (cf. issue #121 )
## To integrate new features
A. I would be nice that the combination of NumPy/SciPy/Bob roughly provides the same functionalities as the Matlab built-in functions. It would also be good to use similar function names such that it is easy for a user to move accross these platforms. A (too exhaustive) list can be found here: http://www.mathworks.ch/ch/help/matlab/functionlist.html
B. More Machine Learning algorithms:
B.1 In particular to add a Hidden Markov Model implementation, as there was one in late Torch 3.
B.2. To add a deformable and parts-based object recognition system (Felzenszwalb-like)
~~B.3 Integration of the i-vector framework~~ (Already done by Laurent)
C. More Audio Processing features:
C.1 Possibility to ~~compute and~~ plot spectrograms (Already done)
C.2 Audio codec to deal with wav and sphere files
C.3 Provide a bridge to HTK
C.4 Boosted Binary Features (cf. Anindya's thesis)
D. Image Processing Tools
~~D.1 GLCM features (Grey-Level Co-occurence Matrix)~~ (Already done by Ivana)
E. ~~Make compiling C++ bindings on satellite packages easier - we can move most of the functionality currently implemented on those packages like https://github/com/bioidiap/xbob.optflow.liu to the core of Bob.~~ (done by André)
F. New metrics: F1-score, precision and recall; cost versus training set size - This should be simple and an excellent coding exercise. If anyone wants to give it a go, please let me know. More info: http://en.wikipedia.org/wiki/F1_score
G. Better use of optimization library (L-BFGS-B) for NNet backprop implementation - this is a somewhat larger piece of work that goes around revisiting the NNet implementation to separate the optimizer from the trainer.
## To be more widely supported
1. ~~To make the Windows/Cygwin port functional~~ (cf. issue #82 )
2. To generate RPM like package:
* For Fedora: http://koji.fedoraproject.org/koji/
* For Suse: https://build.opensuse.org/
3. To generate a package for the TinyCore distribution: http://distro.ibiblio.org/tinycorelinux/downloads.html
In particular, it would be nice to automatize the process of generating a VirtualBox VDI with bob install, potentially based on the tiny linux distribution TinyCore.v1.2https://gitlab.idiap.ch/bob/bob.devtools/-/issues/13Template for MANIFEST.in not found2019-02-12T12:41:19ZGuillaume HEUSCHTemplate for MANIFEST.in not foundHi,
I just tried to create a new pacakge from scratch with this nice new tool:
```bash
bdt new -t "IEEE TBIOM FARGO Paper Companion Package" -o bob.paper.fargo_tbiom_2019 bob/bob.paper.fargo_tbiom_2019 "Guillaume Heusch" "guillaume.he...Hi,
I just tried to create a new pacakge from scratch with this nice new tool:
```bash
bdt new -t "IEEE TBIOM FARGO Paper Companion Package" -o bob.paper.fargo_tbiom_2019 bob/bob.paper.fargo_tbiom_2019 "Guillaume Heusch" "guillaume.heusch@idiap.ch"
```
Here's the result
```bash
Traceback (most recent call last):
File "/idiap/user/heusch/miniconda2/envs/bdt/bin/bdt", line 11, in <module>
sys.exit(main())
File "/idiap/user/heusch/miniconda2/envs/bdt/lib/python3.6/site-packages/click/core.py", line 764, in __call__
return self.main(*args, **kwargs)
File "/idiap/user/heusch/miniconda2/envs/bdt/lib/python3.6/site-packages/click/core.py", line 717, in main
rv = self.invoke(ctx)
File "/idiap/user/heusch/miniconda2/envs/bdt/lib/python3.6/site-packages/click/core.py", line 1137, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/idiap/user/heusch/miniconda2/envs/bdt/lib/python3.6/site-packages/click/core.py", line 956, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/idiap/user/heusch/miniconda2/envs/bdt/lib/python3.6/site-packages/click/core.py", line 555, in invoke
return callback(*args, **kwargs)
File "/idiap/user/heusch/miniconda2/envs/bdt/lib/python3.6/site-packages/bob/devtools/scripts/bdt.py", line 42, in _decorator
value = view_func(*args, **kwargs)
File "/idiap/user/heusch/miniconda2/envs/bdt/lib/python3.6/site-packages/bob/devtools/scripts/new.py", line 150, in new
render_template(env, k, context, output_dir)
File "/idiap/user/heusch/miniconda2/envs/bdt/lib/python3.6/site-packages/bob/devtools/scripts/new.py", line 59, in render_template
T = jenv.get_template(template)
File "/idiap/user/heusch/miniconda2/envs/bdt/lib/python3.6/site-packages/jinja2/environment.py", line 830, in get_template
return self._load_template(name, self.make_globals(globals))
File "/idiap/user/heusch/miniconda2/envs/bdt/lib/python3.6/site-packages/jinja2/environment.py", line 804, in _load_template
template = self.loader.load(self, name, globals)
File "/idiap/user/heusch/miniconda2/envs/bdt/lib/python3.6/site-packages/jinja2/loaders.py", line 113, in load
source, filename, uptodate = self.get_source(environment, name)
File "/idiap/user/heusch/miniconda2/envs/bdt/lib/python3.6/site-packages/jinja2/loaders.py", line 235, in get_source
raise TemplateNotFound(template)
jinja2.exceptions.TemplateNotFound: MANIFEST.in
```
So it seems that the script is looking for `MANIFEST.in` template, which does not exists ...
Thanks !André AnjosAndré Anjoshttps://gitlab.idiap.ch/bob/bob.devtools/-/issues/12Cross-talk between builds on mac builders2019-02-11T07:31:48ZAndré AnjosCross-talk between builds on mac buildersFor some reason, on the mac builders, there is some cross-talk happening between different build directories.
Listing `~/.conda` for the gitlab user, I see where that potentially comes from:
Contents of `~/.conda/envs.txt`:
```sh
sh c...For some reason, on the mac builders, there is some cross-talk happening between different build directories.
Listing `~/.conda` for the gitlab user, I see where that potentially comes from:
Contents of `~/.conda/envs.txt`:
```sh
sh cat .conda/environments.txt
/Users/gitlab/builds/f6f95b82/0/bob/bob.conda/miniconda
/Users/gitlab/builds/f6f95b82/0/bob/bob.ip.annotator/miniconda/envs/bdt
/Users/gitlab/builds/f6f95b82/0/bob/bob.devtools/miniconda
```
Example broken build (notice the package is being built within bob.conda!): https://gitlab.idiap.ch/bob/bob.ip.annotator/-/jobs/156398André AnjosAndré Anjoshttps://gitlab.idiap.ch/bob/bob.ip.annotator/-/issues/1Issue with docomentation2019-02-08T21:30:18ZTeodors EGLITISIssue with docomentationSeams to be an issue, for the time being commented the line in `` ./doc/annotater.rst``
If line is present, there is such warning:
<>/bob.ip.annotator/bob/ip/annotator/__init__.py:docstring of bob.ip.annotator.get_config:0:
...Seams to be an issue, for the time being commented the line in `` ./doc/annotater.rst``
If line is present, there is such warning:
<>/bob.ip.annotator/bob/ip/annotator/__init__.py:docstring of bob.ip.annotator.get_config:0:
WARNING: duplicate object description of bob.ip.annotator.get_config,
other instance in <>/bob.ip.annotator/doc/annotator.rst,
use :noindex: for one of them
Unfortunately I don't have any idea how to solve this.André AnjosAndré Anjoshttps://gitlab.idiap.ch/bob/bob.ip.annotator/-/issues/6There is no undo/redo functionality2019-02-06T13:17:30ZAndré AnjosThere is no undo/redo functionalityIf one is annotating a very large or complex set of objects, adding undo/redo can be a time saver.
One possible way to implement a simple undo/redo stack would be to insert `lambda`'s that redo/undo the last action using the "command pa...If one is annotating a very large or complex set of objects, adding undo/redo can be a time saver.
One possible way to implement a simple undo/redo stack would be to insert `lambda`'s that redo/undo the last action using the "command pattern" design.https://gitlab.idiap.ch/bob/bob.ip.annotator/-/issues/5Point insertion is a far-from-obvious operation2019-02-05T08:57:39ZAndré AnjosPoint insertion is a far-from-obvious operationCurrently, this application only supports inserting a point **before** another one. If you try to insert it after some other point, an unexpected order issue will occur.
It would be nice to have this fixed by properly calculating the s...Currently, this application only supports inserting a point **before** another one. If you try to insert it after some other point, an unexpected order issue will occur.
It would be nice to have this fixed by properly calculating the second closest point and figuring out if the new point needs to be insert before of after the currently active point.André AnjosAndré Anjoshttps://gitlab.idiap.ch/bob/bob.ip.annotator/-/issues/4Tooltips now working on macOS2019-02-05T04:47:05ZAndré AnjosTooltips now working on macOSThe tooltip class works fine on Linux, but is not showing up on macOS.The tooltip class works fine on Linux, but is not showing up on macOS.André AnjosAndré Anjoshttps://gitlab.idiap.ch/bob/bob.ip.pytorch_extractor/-/issues/3the master branch is broken2019-02-04T15:37:46ZOlegs NIKISINSthe master branch is brokenHello @heusch,
The master branch of this package is broken. Not sure if you are aware of this, thus opening an issue. Probably ``bob.learn.pytorch`` should be updated. Thanks!Hello @heusch,
The master branch of this package is broken. Not sure if you are aware of this, thus opening an issue. Probably ``bob.learn.pytorch`` should be updated. Thanks!https://gitlab.idiap.ch/bob/bob.ip.annotator/-/issues/2Undocumented functionality with L-ALT key2019-02-04T09:58:44ZJaden DIEFENBAUGHUndocumented functionality with L-ALT keyThere seems to be an undocumented feature: holding left-alt will show you the number of each annotation point and shade the annotation area. Maybe just add a note in the help menu about this?There seems to be an undocumented feature: holding left-alt will show you the number of each annotation point and shade the annotation area. Maybe just add a note in the help menu about this?https://gitlab.idiap.ch/bob/bob.ip.annotator/-/issues/3Feature request - editing arbitrary annotation points2019-02-04T09:58:23ZJaden DIEFENBAUGHFeature request - editing arbitrary annotation pointsIt would be really nice to be able to be able to cycle through all the points to edit/delete any arbitrary point (maybe *shift+j* & *shift+k*?)...sometimes it's hard to tell a point's accuracy until a couple points later.It would be really nice to be able to be able to cycle through all the points to edit/delete any arbitrary point (maybe *shift+j* & *shift+k*?)...sometimes it's hard to tell a point's accuracy until a couple points later.https://gitlab.idiap.ch/bob/bob.devtools/-/issues/11Skip private channels while bootstrapping or it will install a very old versi...2019-01-28T10:02:23ZAndré AnjosSkip private channels while bootstrapping or it will install a very old version of `bdt`See an example here: https://gitlab.idiap.ch/bob/bob.ip.annotator/-/jobs/155752
Obviously, conda resolution orders takes channel into priority rather than version...See an example here: https://gitlab.idiap.ch/bob/bob.ip.annotator/-/jobs/155752
Obviously, conda resolution orders takes channel into priority rather than version...André AnjosAndré Anjoshttps://gitlab.idiap.ch/bob/bob.devtools/-/issues/10Follow-up from "[setup] Pin click>=7 and fixes #9"2019-01-28T09:38:43ZAmir MOHAMMADIFollow-up from "[setup] Pin click>=7 and fixes #9"The following discussion from !3 should be addressed:
- [ ] @amohammadi started a [discussion](https://gitlab.idiap.ch/bob/bob.devtools/merge_requests/3#note_37949):
> @andre.anjos from the comments just above this change: `These ...The following discussion from !3 should be addressed:
- [ ] @amohammadi started a [discussion](https://gitlab.idiap.ch/bob/bob.devtools/merge_requests/3#note_37949):
> @andre.anjos from the comments just above this change: `These versions **should** match the versions inside bob-devel recipe.`
@andre.anjos you cannot update click version in conda_build_config.yaml without updating bob-devel first.André AnjosAndré Anjoshttps://gitlab.idiap.ch/bob/bob.devtools/-/issues/9Build command fails, complaining about zstd2019-01-25T14:54:02ZJaden DIEFENBAUGHBuild command fails, complaining about zstdRunning `bdt build --help` gets:
```
read filter "zstd" is not supported
write filter "zstd" is not supported
Usage: bdt build [OPTIONS]
Warning: entry point could not be loaded. Contact its author for help.
Traceback (most recent ...Running `bdt build --help` gets:
```
read filter "zstd" is not supported
write filter "zstd" is not supported
Usage: bdt build [OPTIONS]
Warning: entry point could not be loaded. Contact its author for help.
Traceback (most recent call last):
File "/home/jae/miniconda3/envs/bdt/lib/python3.6/site-packages/click_plugins/core.py", line 37, in decorator
group.add_command(entry_point.load())
File "/home/jae/miniconda3/envs/bdt/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2318, in load
return self.resolve()
File "/home/jae/miniconda3/envs/bdt/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2324, in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
File "/home/jae/miniconda3/envs/bdt/lib/python3.6/site-packages/bob/devtools/scripts/build.py", line 75, in <module>
@bdt.raise_on_error
File "/home/jae/miniconda3/envs/bdt/lib/python3.6/site-packages/click/decorators.py", line 170, in decorator
_param_memo(f, OptionClass(param_decls, **attrs))
File "/home/jae/miniconda3/envs/bdt/lib/python3.6/site-packages/click/core.py", line 1460, in __init__
Parameter.__init__(self, param_decls, type=type, **attrs)
TypeError: __init__() got an unexpected keyword argument 'hidden'
Options:
-h, -?, --help Show this message and exit.
```
I get those first two lines about read/write filters with every `bdt` command I try, even just `bdt --help`.
Here's the conda environment (updated as of Jan. 23rd):
```
# Name Version Build Channel
alabaster 0.7.11 py36_0 defaults
asn1crypto 0.24.0 py36_0 defaults
babel 2.6.0 py36_0 defaults
beautifulsoup4 4.7.1 py36_1 defaults
bob 5.0.0 py36hc3b47e9_0 https://www.idiap.ch/software/bob/conda
bob.devtools 0.1.2 py36h6b6bea4_0 https://www.idiap.ch/software/bob/conda
bzip2 1.0.6 h14c3975_5 defaults
ca-certificates 2018.03.07 0 defaults
certifi 2018.4.16 py36_0 defaults
cffi 1.11.5 py36h9745a5d_0 defaults
chardet 3.0.4 py36h0f667ec_1 defaults
click 6.7 py36h5253387_0 defaults
click-plugins 1.0.3 py36_0 defaults
conda 4.5.12 py36_0 defaults
conda-build 3.17.7 py36_0 defaults
conda-env 2.6.0 1 defaults
cryptography 2.2.2 py36h14c3975_0 defaults
docutils 0.14 py36hb0f60f5_0 defaults
filelock 3.0.10 py36_0 defaults
gitdb2 2.0.5 py36_0 defaults
gitpython 2.1.11 py36_0 defaults
glob2 0.6 py36_1 defaults
icu 58.2 h9c2bf20_1 defaults
idna 2.7 py36_0 defaults
imagesize 1.0.0 py36_0 defaults
jinja2 2.10 py36ha16c418_0 defaults
libarchive 3.3.2 hb43526a_6 defaults
libedit 3.1.20170329 h6b74fdf_2 defaults
libffi 3.2.1 hd88cf55_4 defaults
libgcc-ng 7.2.0 hdf63c60_3 defaults
liblief 0.9.0 h1532aa0_0 defaults
libstdcxx-ng 7.2.0 hdf63c60_3 defaults
libxml2 2.9.8 h26e45fe_1 defaults
libxslt 1.1.32 h1312cb7_0 defaults
lxml 4.2.4 py36hf71bdeb_0 defaults
lz4-c 1.8.1.2 h14c3975_0 defaults
lzo 2.10 h49e0be7_2 defaults
markupsafe 1.0 py36hd9260cd_1 defaults
ncurses 6.1 hf484d3e_0 defaults
openssl 1.0.2o h20670df_0 defaults
patchelf 0.9 hf484d3e_2 defaults
pip 18.1 py36_0 defaults
pkginfo 1.5.0.1 py36_0 defaults
psutil 5.4.6 py36h14c3975_0 defaults
py-lief 0.9.0 py36h1532aa0_0 defaults
pycosat 0.6.3 py36h14c3975_0 defaults
pycparser 2.18 py36hf9f622e_1 defaults
pygments 2.2.0 py36h0d3125c_0 defaults
pyopenssl 18.0.0 py36_0 defaults
pysocks 1.6.8 py36_0 defaults
python 3.6.6 hc3d631a_0 defaults
python-dateutil 2.7.3 py36_0 defaults
python-gitlab 1.7.0 py36_0 https://www.idiap.ch/software/bob/conda
python-libarchive-c 2.8 py36_6 defaults
pytz 2018.5 py36_0 defaults
pyyaml 3.12 py36hafb9ca4_1 defaults
readline 7.0 ha6073c6_4 defaults
requests 2.19.1 py36_0 defaults
requests-toolbelt 0.8.0 py36_0 defaults
ruamel_yaml 0.15.46 py36h14c3975_0 defaults
setuptools 39.2.0 py36_0 defaults
six 1.11.0 py36h372c433_1 defaults
smmap2 2.0.5 py36_0 defaults
snowballstemmer 1.2.1 py36h6febd40_0 defaults
soupsieve 1.7.1 py36_0 defaults
sphinx 1.6.3 py36he5f0bdb_0 defaults
sphinxcontrib 1.0 py36h6d0f590_1 defaults
sphinxcontrib-websupport 1.1.0 py36_1 defaults
sqlite 3.24.0 h84994c4_0 defaults
tk 8.6.7 hc745277_3 defaults
tqdm 4.29.1 py_0 defaults
twine 1.11.0 py36_0 defaults
typing 3.6.4 py36_0 defaults
urllib3 1.23 py36_0 defaults
wheel 0.32.3 py36_0 defaults
xz 5.2.4 h14c3975_4 defaults
yaml 0.1.7 had09818_2 defaults
zlib 1.2.11 ha838bed_2 defaults
zstd 1.3.3 h84994c4_0 defaults
```André AnjosAndré Anjoshttps://gitlab.idiap.ch/bob/bob.devtools/-/issues/6Please organize the development docs from here2019-01-25T14:42:20ZAmir MOHAMMADIPlease organize the development docs from hereAs discussed with @andre.anjos before, the docs in the template folder of bob.admin should go to bob.extension.As discussed with @andre.anjos before, the docs in the template folder of bob.admin should go to bob.extension.Conda-based CIAndré AnjosAndré Anjos