OwlCyberSecurity - MANAGER
Edit File: test_numpy_version.cpython-311.pyc
� ��bg' � �2 � d Z ddlZddlZddlmZ d� Zd� ZdS )aY Check the numpy version is valid. Note that a development version is marked by the presence of 'dev0' or '+' in the version string, all else is treated as a release. The version string itself is set from the output of ``git describe`` which relies on tags. Examples -------- Valid Development: 1.22.0.dev0 1.22.0.dev0+5-g7999db4df2 1.22.0+5-g7999db4df2 Valid Release: 1.21.0.rc1, 1.21.0.b1, 1.21.0 Invalid: 1.22.0.dev, 1.22.0.dev0-5-g7999db4dfB, 1.21.0.d1, 1.21.a Note that a release is determined by the version string, which in turn is controlled by the result of the ``git describe`` command. � N)�assert_c � � d} d}t j j r#t j | dz t j � � }n%t j | |z dz t j � � }t |d ut j � � d S )Nz/^[0-9]+\.[0-9]+\.[0-9]+(a[0-9]|b[0-9]|rc[0-9]|)z (\.dev0|)(\+[0-9]*\.g[0-9a-f]+|)�$)�np�version�release�re�match� __version__r )�version_pattern� dev_suffix�ress �q/builddir/build/BUILD/cloudlinux-venv-1.0.7/venv/lib64/python3.11/site-packages/numpy/tests/test_numpy_version.py�test_valid_numpy_versionr sp � � I�O�4�J� �z�� K��h���,�b�n�=�=����h���3�c�9�2�>�J�J�� �C�t�O�R�^�,�,�,�,�,� c � � t j j r/t t j t j j k d� � d S t t j � d� � d t j j k d� � d S )Nz)short_version mismatch in release version�+r z-short_version mismatch in development version)r r r r r � short_version�split� r r �test_short_versionr % s� � � �z�� A����"�*�":�:�;� =� =� =� =� =� ���$�$�S�)�)�!�,�� �0H�H�?� A� A� A� A� Ar )�__doc__r �numpyr � numpy.testingr r r r r r �<module>r se ��� �" � � � � � � � � !� !� !� !� !� !� -� -� -�A� A� A� A� Ar