web2py version number

50 views
Skip to first unread message

Niphlod

unread,
Feb 6, 2015, 3:38:26 PM2/6/15
to web2py-d...@googlegroups.com
Hi, I noticed that travis is reporting some deprecationerrors ....

the relevant bits are

Obtaining file:///home/travis/build/web2py/web2py

/home/travis/virtualenv/python2.6.9/lib/python2.6/site-packages/setuptools/dist.py:292: UserWarning: The version specified ('2.9.12-stable+timestamp.2015.01.17.00.07.04') is an invalid version, this may not work as expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 for more details.

"details." % self.metadata.version

/home/travis/build/web2py/web2py/setup.py:12: DeprecationWarning: Parameters to load are deprecated. Call .resolve and .require separately.

"""Installing collected packages: web2py
Running setup.py develop for web2py

/home/travis/virtualenv/python2.6.9/lib/python2.6/site-packages/setuptools/dist.py:292: UserWarning: The version specified ('2.9.12-stable+timestamp.2015.01.17.00.07.04') is an invalid version, this may not work as expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 for more details.

"details." % self.metadata.version

/home/travis/virtualenv/python2.6.9/lib/python2.6/site-packages/pkg_resources/__init__.py:2510: PEP440Warning: 'web2py (2.9.12-stable-timestamp.2015.01.17.00.07.04)' is being parsed as a legacy, non PEP 440, version. You may find odd behavior and sort order. In particular it will be sorted as less than 0.0. It is recommend to migrate to PEP 440 compatible versions.

PEP440Warning,

/home/travis/virtualenv/python2.6.9/lib/python2.6/site-packages/setuptools/command/egg_info.py:171: DeprecationWarning: Parameters to load are deprecated. Call .resolve and .require separately.

writer = ep.load(installer=installer)

Creating /home/travis/virtualenv/python2.6.9/lib/python2.6/site-packages/web2py.egg-link (link to .)

Adding web2py 2.9.12-stable-timestamp.2015.01.17.00.07.04 to easy-install.pth file

Installed /home/travis/build/web2py/web2py

there's still time but it'll better solve this ASAP, especially if we want to revemp the concept of being able to put stable releases on pipy.



Reply all
Reply to author
Forward
0 new messages