B
    G[f                 @   sh  yd dl mZ W n6 ek
rF   ed ddddddd	d
dddgZY nX yd dlmZ W n ek
r   ed ddhdddddddddddddhdd d!d"d#d$d%d&d'd(d)d*d+d,d-d.d/d0d1d2hd3d4d5d6d7hdd3d8d9dd-d:d2hd;d<d=d>d?hd@dAdBdCdDhdEdFdGdHd=dIdJdKdLdMh
dNdOdPhdQ	ZY nX dRdSdTdUdVdWdXdYZdZd[d\d]d^d_d`dadbdcdddedfdgdhdidjdkdldmdnZdoZ	dpS )q    )allowed_license_familieszpwarning: could not import conda-build ALLOWED_LICENSE_FAMILIES data.  Falling back to possibly stale static listZAGPLZGPL2ZGPL3ZLGPLZBSDZMITZApacheZPSFzPublic-DomainZProprietaryZOther)FIELDSz]warning: could not import conda-build FIELDS data.  Falling back to possibly stalestatic listnameversionfnZurlZmd5Zsha1Zsha256Zgit_urlZgit_tagZ
git_branchZgit_revZpatchesZhg_urlZhg_tagpathZfeaturesZtrack_featuresskipZnumberZentry_pointsZ
osx_is_appZnoarchZpreserve_egg_dirZwin_has_prefixZno_linkZignore_prefix_filesZmsvc_compilerZskip_compile_pycZdetect_binary_files_with_prefixZscriptZalways_include_filesZbinary_relocationZbinary_has_prefix_filesZnoarch_pythonZrun_exportsbuildrunZpreferred_envZhostZpreferred_env_executable_pathsabouttestrequirementsentryZiconZsummarytypeZcli_optsZrequiresZcommandsfilesZsource_filesZimportslicenseZlicense_urlZlicense_familyZlicense_fileZdescriptionhomeZdoc_urlZdoc_source_urlZdev_urlzrecipe-maintainersfinalZparent_recipe)	packagesourcer	   r   ZoutputsZappr   r   ZextrazMachO-universalz
MachO-i386zMachO-x86_64z	MachO-ppczMachO-ppc64ZDLLZELF)s   s   s   s   s   s   MZ s   ELFZUNKNOWNZAM33ZAMD64ZARMZEBCZI386ZIA64ZM32RZMIPS16ZMIPSFPUZ	MIPSFPU16ZPOWERPCZ	POWERPCFPZR4000ZSH3ZSH3DSPZSH4ZSH5ZTHUMBZ	WCEMIPSV2)r   i  id  i  i  iL  i   iA  if  if  if  i  i  if  i  i  i  i  i  ii  a9  
# Note: there are many handy hints in comments in this example -- remove them when you've finalized your recipe
# Jinja variables help maintain the recipe as you'll update the version only here.
# sha256 is the prefered checksum -- you can get it for a file with:
#  `openssl sha256 <file name>`.
# You may need the openssl package, available on conda-forge
#  `conda install openssl -c conda-forge``
# If the installation is complex, or different between Unix and Windows, use separate bld.bat and build.sh files instead of this key.
# By default, the package will be built for the Python versions supported by conda-forge and for all major OSs.
# Add the line "skip: True  # [py<35]" (for example) to limit to Python 3.5 and newer, or "skip: True  # [not win]" to limit to Windows.
# When setuptools is available add the `--single-version-externally-managed --record record.txt` above.
# if your project compiles code (such as a C extension) then add `toolchain` as a build requirement.
# Some package might need a `test/commands` key to check CLI.
# List all the packages/modules that `run_test.py` imports.
# Remember to specify the license variants for BSD, Apache, GPL, and LGLP.
# Prefer the short version, e.g: GPL-2.0 instead of GNU General Public License version 2.0
# See https://opensource.org/licenses/alphabetical
# The license_family, i.e. "BSD" if license is "BSD-3-Clause". (optional)
# It is strongly encouraged to include a license file in the package,
# (even if the license doesn't require it) using the license_file entry.
# See http://conda.pydata.org/docs/building/meta-yaml.html#license-file
# The remaining entries in this section are optional, but recommended
# GitHub IDs for maintainers of the recipe.
# Always check with the people listed below if they are OK becoming maintainers of the recipe. (There will be spam!)
N)
Zconda_build.license_familyr   ZLICENSE_FAMILIESImportErrorprintZconda_build.metadatar   ZMAGIC_HEADERSZ	DLL_TYPESZCONDA_FORGE_COMMENTS r   r   5lib/python3.7/site-packages/conda_verify/constants.py<module>   sV   


