conda-forge / python-snappy-feedstock

A conda-smithy repository for python-snappy.

About python-snappy-feedstock

Feedstock license: BSD-3-Clause

Home: https://github.com/intake/python-snappy

Package license: BSD-3-Clause

Summary: Python library for the snappy compression library from Google

Development: https://github.com/intake/python-snappy

Current build status

All platforms:

Current release info

Name	Downloads	Version	Platforms

Installing python-snappy

Installing python-snappy from the conda-forge channel can be achieved by adding conda-forge to your channels with:

conda config --add channels conda-forge
conda config --set channel_priority strict

Once the conda-forge channel has been enabled, python-snappy can be installed with conda:

conda install python-snappy

or with mamba:

mamba install python-snappy

It is possible to list all of the versions of python-snappy available on your platform with conda:

conda search python-snappy --channel conda-forge

or with mamba:

mamba search python-snappy --channel conda-forge

Alternatively, mamba repoquery may provide more information:

# Search all versions available on your platform:
mamba repoquery search python-snappy --channel conda-forge

# List packages depending on `python-snappy`:
mamba repoquery whoneeds python-snappy --channel conda-forge

# List dependencies of `python-snappy`:
mamba repoquery depends python-snappy --channel conda-forge

About conda-forge

conda-forge is a community-led conda channel of installable packages. In order to provide high-quality builds, the process has been automated into the conda-forge GitHub organization. The conda-forge organization contains one repository for each of the installable packages. Such a repository is known as a feedstock.

A feedstock is made up of a conda recipe (the instructions on what and how to build the package) and the necessary configurations for automatic building using freely available continuous integration services. Thanks to the awesome service provided by Azure, GitHub, CircleCI, AppVeyor, Drone, and TravisCI it is possible to build and upload installable packages to the conda-forge anaconda.org channel for Linux, Windows and OSX respectively.

To manage the continuous integration and simplify feedstock maintenance conda-smithy has been developed. Using the conda-forge.yml within this repository, it is possible to re-render all of this feedstock's supporting files (e.g. the CI configuration files) with conda smithy rerender.

For more information please check the conda-forge documentation.

Terminology

feedstock - the conda recipe (raw material), supporting scripts and CI configuration.

conda-smithy - the tool which helps orchestrate the feedstock. Its primary use is in the construction of the CI .yml files and simplify the management of many feedstocks.

conda-forge - the place where the feedstock and smithy live and work to produce the finished article (built conda distributions)

Updating python-snappy-feedstock

If you would like to improve the python-snappy recipe or build a new package version, please fork this repository and submit a PR. Upon submission, your changes will be run on the appropriate platforms to give the reviewer an opportunity to confirm that the changes result in a successful build. Once merged, the recipe will be re-built and uploaded automatically to the conda-forge channel, whereupon the built conda packages will be available for everybody to install and use from the conda-forge channel. Note that all branches in the conda-forge/python-snappy-feedstock are immediately built and any created packages are uploaded, so PRs should be based on branches in forks and branches in the main repository should only be used to build distinct package versions.

In order to produce a uniquely identifiable distribution:

• If the version of a package is not being increased, please add or increase the build/number.
• If the version of a package is being increased, please remember to return the build/number back to 0.

Feedstock Maintainers

• @djsutherland
• @mariusvniekerk
• @martindurant

python-snappy-feedstock's Issues

No python 3.6 version for linux (or windows)

I notice that a package was built for py36, osx in early January.
Can I please request a py36, linux64 package also?

@conda-forge-admin , please re-render

@conda-forge-admin , please re-render

conda-forge packaging for python-snappy 0.6.0?

• I read the conda-forge documentation and could not find the solution for my problem there.

Issue:

Just wondering if there are plans to package python-snappy 0.6.0 on conda-forge, or if there's some reason what that's blocked from happening or undesirable. It's been out for ~2 months on the default conda channel

Thanks!

`bot` key should be a top-level key

Looks like the bot key wound up under build_platform. Though it is a top-level key ( ref )

python-snappy-feedstock/conda-forge.yml

Lines 1 to 6 in dc0e8b7

	build_platform:
	linux_aarch64: linux_64
	linux_ppc64le: linux_64
	osx_arm64: osx_64
	bot:
	inspection: grayskull-update

conda-forge packaging for linux-aarch64

• [ x ] I read the conda-forge documentation and could not find the solution for my problem there.

Issue:

python-snappy isn't available for linux-aarch64. It seems like most conda-forge packages are available across all platforms; is there any chance this one will be added?

Package is `noarch: python` and is using compilers

In PR ( #39 ), this package was converted to noarch: python

python-snappy-feedstock/recipe/meta.yaml

Lines 13 to 16 in dbf939b

	build:
	number: 0
	script: {{ PYTHON }} -m pip install . --no-deps -vv
	noarch: python

However it still depends on compilers

python-snappy-feedstock/recipe/meta.yaml

Lines 18 to 23 in dbf939b

	requirements:
	build:
	- python # [build_platform != target_platform]
	- cross-python_{{ target_platform }} # [build_platform != target_platform]
	- {{ compiler('c') }}
	- {{ compiler('cxx') }}

If this package is pure Python and OS independent, we can drop the requirements/build section

If the package still has Python or OS dependence, we may need to do something else

Please let me know which it is

AttributeError: module 'snappy' has no attribute 'compress'

I am trying to play around with the datashader examples and when I go to import I get the following errors.. bellow is all the code and entire error message.

import datashader as ds
import datashader.transfer_functions as tf
import dask.dataframe as dd
import numpy as np
import pandas as pd

RETURN>>>

[AttributeError                            Traceback (most recent call last)
<ipython-input-4-d9e8607b1310> in <module>()
----> 1 import datashader as ds
      2 import datashader.transfer_functions as tf
      3 import dask.dataframe as dd
      4 import numpy as np
      5 import pandas as pd

/home/mcamp/anaconda3/lib/python3.5/site-packages/datashader/__init__.py in <module>()
      3 __version__ = '0.3.0'
      4 
----> 5 from .core import Canvas
      6 from .reductions import (count, any, sum, min, max, mean, std, var, count_cat,
      7                          summary)

/home/mcamp/anaconda3/lib/python3.5/site-packages/datashader/core.py in <module>()
      3 import numpy as np
      4 from datashape.predicates import istabular
----> 5 from odo import discover
      6 from xarray import DataArray, align
      7 

/home/mcamp/anaconda3/lib/python3.5/site-packages/odo/__init__.py in <module>()
     63     from .backends.url import URL
     64 with ignoring(ImportError):
---> 65     from .backends.dask import dask
     66 
     67 

/home/mcamp/anaconda3/lib/python3.5/site-packages/odo/backends/dask.py in <module>()
      8 
      9 from dask.array.core import Array, from_array
---> 10 from dask.bag.core import Bag
     11 import dask.bag as db
     12 from dask.compatibility import long

/home/mcamp/anaconda3/lib/python3.5/site-packages/dask/bag/__init__.py in <module>()
      1 from __future__ import absolute_import, division, print_function
      2 
----> 3 from .core import (Bag, Item, from_sequence, from_url, to_textfiles, concat,
      4                    from_delayed, bag_range as range, bag_zip as zip)
      5 from .text import read_text

/home/mcamp/anaconda3/lib/python3.5/site-packages/dask/bag/core.py in <module>()
     39 from ..utils import (open, system_encoding, takes_multiple_arguments, funcname,
     40                      digit, insert)
---> 41 from ..bytes.core import write_bytes
     42 
     43 

/home/mcamp/anaconda3/lib/python3.5/site-packages/dask/bytes/__init__.py in <module>()
      2 
      3 from ..utils import ignoring
----> 4 from .core import read_bytes, open_files, open_text_files
      5 
      6 from . import local

/home/mcamp/anaconda3/lib/python3.5/site-packages/dask/bytes/core.py in <module>()
      7 from warnings import warn
      8 
----> 9 from .compression import seekable_files, files as compress_files
     10 from .utils import SeekableFile, read_block
     11 from ..compatibility import PY2, unicode

/home/mcamp/anaconda3/lib/python3.5/site-packages/dask/bytes/compression.py in <module>()
     30 with ignoring(ImportError):
     31     import snappy
---> 32     compress['snappy'] = snappy.compress
     33     decompress['snappy'] = snappy.decompress
     34 

AttributeError: module 'snappy' has no attribute 'compress'](url)

Snappy 1.1.8

Issue:
It seems python-snappy requires snappy>=1.1.7,<1.1.8.0a0 according to conda solver:

UnsatisfiableError: The following specifications were found to be incompatible w
ith each other:



Package snappy conflicts for:
arrow-cpp==0.16.0=py37h750224e_1 -> snappy[version='>=1.1.8,<2.0a0']
parquet-cpp==1.5.1=2 -> arrow-cpp[version='>=0.11.0'] -> snappy[version='>=1.1.7
,<1.1.8.0a0|>=1.1.8,<2.0a0']
python-snappy==0.5.4=py37hd25c944_1 -> snappy[version='>=1.1.7,<1.1.8.0a0']
pyarrow==0.16.0=py37hecaa37c_2 -> arrow-cpp[version='>=0.16.0,<0.16.1.0a0'] -> s
nappy[version='>=1.1.8,<2.0a0']
pyarrow==0.16.0=py37hecaa37c_2 -> snappy
snappy==1.1.8=he025d50_1

This is weird since source repository states requirements are snappy library >= 1.0.2 (or revision 27) and it prevents using python-snappy with newer packages.

Details about conda and system ( conda info ):

     active environment : base
    active env location : C:\Users\user\AppData\Local\Continuum\miniconda3
            shell level : 1
       user config file : C:\Users\user\.condarc
 populated config files : C:\Users\user\.condarc
          conda version : 4.8.0
    conda-build version : not installed
         python version : 3.6.7.final.0
       virtual packages :
       base environment : C:\Users\user\AppData\Local\Continuum\miniconda3
 (writable)
           channel URLs : file:///channel/win-64
                          file:///channel/noarch
          package cache : C:\Users\user\AppData\Local\Continuum\miniconda3\
pkgs
                          C:\Users\user\.conda\pkgs
                          C:\Users\user\AppData\Local\conda\conda\pkgs
       envs directories : C:\Users\user\AppData\Local\Continuum\miniconda3\
envs
                          C:\Users\user\.conda\envs
                          C:\Users\user\AppData\Local\conda\conda\envs
               platform : win-64
             user-agent : conda/4.8.0 requests/2.23.0 CPython/3.6.7 Windows/2008
ServerR2 Windows/6.1.7601
          administrator : True
             netrc file : None
           offline mode : True

Details may look unusual since I use a local channel with packages from conda-forge to update miniconda on a server without Internet access.