????
| Current Path : /usr/lib/python2.7/site-packages/wheel/ |
| Current File : //usr/lib/python2.7/site-packages/wheel/wininst2wheel.pyc |
�
��]c @ s� d d l Z d d l Z d d l Z d d l Z d d l Z d d l Z d d l Z d d l
m Z d d l m
Z
d d l m Z d d l m Z d d l m Z e j d e j � Z d � Z e j j d � Z d
� Z e d k r� e � n d S( i����N( t make_archive( t rmtree( t archive_wheelfile( t ArgumentParser( t iglobsX (^|/)(?P<name>[^/]+?)-(?P<ver>.+?)
(-(?P<pyver>.+?))?(-(?P<arch>.+?))?.egg-info(/|$)c
C s@ d
} | r: t j | � } | s: t d | f � � q: n | j d � \ } } } | sn t d | f � � n | d } | j d � \ } } } | r� | j d � r� | } | j d d � } n d } | j d � \ } } } | s� t d | f � � n | r!| j d � } | j d
� } n t d | d
| d | d | � S( sx Extract metadata from filenames.
Extracts the 4 metadataitems needed (name, version, pyversion, arch) from
the installer filename and the name of the egg-info directory embedded in
the zipfile (if any).
The egginfo filename has the format::
name-ver(-pyver)(-arch).egg-info
The installer filename has the format::
name-ver.arch(-pyver).exe
Some things to note:
1. The installer filename is not definitive. An installer can be renamed
and work perfectly well as an installer. So more reliable data should
be used whenever possible.
2. The egg-info data should be preferred for the name and version, because
these come straight from the distutils metadata, and are mandatory.
3. The pyver from the egg-info data should be ignored, as it is
constructed from the version of Python used to build the installer,
which is irrelevant - the installer filename is correct here (even to
the point that when it's not there, any version is implied).
4. The architecture must be taken from the installer filename, as it is
not included in the egg-info data.
5. Architecture-neutral installers still have an architecture because the
installer format itself (being executable) is architecture-specific. We
should therefore ignore the architecture if the content is pure-python.
s! Egg info filename %s is not validt -s"