Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • 8978
  • 8938
  • benchmark-all-commits
  • debian_package
  • onepython
  • benchmark_elasticsearch
  • buildpackage
  • debian/platform-0.9
  • release/0.9.x
  • feature/streaming-transfer
  • debian/experimental-0.9
  • debian/experimental
  • debian/platform-0.8
  • bug/remove-unicode-conversion
  • release/0.8.x
  • release/0.7.x
  • release/bitmask-0.9.x-alpha
  • debian/platform-0.7
  • release/0.6.x
  • 0.10.5
  • 0.10.4
  • 0.9.6post3
  • 0.10.3
  • 0.10.2
  • 0.10.1
  • 0.10.0
  • 0.9.3post3
  • 0.9.6post2
  • 0.9.6post1
  • 0.9.6
  • 0.9.5
  • 0.9.3
  • 0.9.2
  • 0.9.1
  • 0.9.0
  • 0.9.0rc1
  • 0.8.1
  • 0.8.0
  • 0.7.4
40 results

__init__.py

Blame
    • drebs's avatar
      3e94cafa
      [pkg] unify client and server into a single python package · 3e94cafa
      drebs authored and Kali Kaneko's avatar Kali Kaneko committed
      We have been discussing about this merge for a while.
      Its main goal is to simplify things: code navigation, but also
      packaging.
      
      The rationale is that the code is more cohesive in this way, and there's
      only one source package to install.
      
      Dependencies that are only for the server or the client will not be
      installed by default, and they are expected to be provided by the
      environment. There are setuptools extras defined for the client and the
      server.
      
      Debianization is still expected to split the single source package into
      3 binaries.
      
      Another avantage is that the documentation can now install a single
      package with a single step, and therefore include the docstrings into
      the generated docs.
      
      - Resolves: #8896
      [pkg] unify client and server into a single python package
      drebs authored and Kali Kaneko's avatar Kali Kaneko committed
      We have been discussing about this merge for a while.
      Its main goal is to simplify things: code navigation, but also
      packaging.
      
      The rationale is that the code is more cohesive in this way, and there's
      only one source package to install.
      
      Dependencies that are only for the server or the client will not be
      installed by default, and they are expected to be provided by the
      environment. There are setuptools extras defined for the client and the
      server.
      
      Debianization is still expected to split the single source package into
      3 binaries.
      
      Another avantage is that the documentation can now install a single
      package with a single step, and therefore include the docstrings into
      the generated docs.
      
      - Resolves: #8896
    __init__.py 0 B