Prev: ports/146626: [PATCH] print/hplip3 gzip files curruption withUSE_DOS2UNIX=yes
Next: ports/146626: commit references a PR
From: chukharev on 17 May 2010 08:54 Hi, It seems than the new version of devel/pylint port is not compatible with the old config files in user's home. At least I was getting an error as in the following. $ pylint --version /usr/local/lib/python2.6/site-packages/logilab_common-0.50.1-py2.6.egg/logilab/common/configuration.py:716: DeprecationWarning: "_config_parser" attribute has been renamed to "cfgfile_parser" warn(msg, DeprecationWarning) Traceback (most recent call last): File "/usr/local/bin/pylint", line 5, in <module> pkg_resources.run_script('pylint==0.20.0', 'pylint') File "build/bdist.freebsd-8.0-STABLE-i386/egg/pkg_resources.py", line 489, in run_script File "build/bdist.freebsd-8.0-STABLE-i386/egg/pkg_resources.py", line 1207, in run_script File "/usr/local/lib/python2.6/site-packages/pylint-0.20.0-py2.6.egg/EGG-INFO/scripts/pylint", line 4, in <module> lint.Run(sys.argv[1:]) File "/usr/local/lib/python2.6/site-packages/pylint-0.20.0-py2.6.egg/pylint/lint.py", line 861, in __init__ linter.load_config_file() File "/usr/local/lib/python2.6/site-packages/logilab_common-0.50.1-py2.6.egg/logilab/common/configuration.py", line 637, in load_config_file provider.set_option(option, value, optdict=optdict) TypeError: set_option() got an unexpected keyword argument 'optdict' Everything work since renaming ~/.pylintrc and ~/.pylint.d. I think this is good to mention in ports/UPDATING. $ uname -a FreeBSD vova-vaio 8.0-STABLE FreeBSD 8.0-STABLE #2: Tue Apr 27 10:16:00 EEST 2010 root(a)vova-vaio:/usr/obj/usr/src/sys/VOVA i386 $ pkg_info -O devel/pylint The following installed package(s) has devel/pylint origin: pylint-py26-0.20.0 Vladimir Chukharev _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Eitan Adler on 17 May 2010 16:46
> personally, I do not think that (incompatibly) changed user options or > configuration settings for this port are 'worth' an entry in UPDATING, > thus I skipped it. UPDATING entries are cheap. It can't hurt to have this as an entry to help users of the port. _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org" |