version

Why does 'pip' require “setuptools >= 0.8” even though I have 2.1 installed?

一笑奈何 提交于 2019-12-04 12:39:24
When I attempt certain commands with pip , I get an error message stating that pip “requires setuptools >= 0.8 for dist-info” even though I have, according to yolk -l (as well as pip list ), a much higher version of setuptools installed: pip - 1.5 - active ... setuptools - 2.1 - active Why is pip asking for a version of setuptools >= 0.8? Isn't 2.1 > 0.8; or is my installation not in fact at the version that yolk is reporting? Is there something I need to do to ensure that I in fact do have "setuptools >= 0.8"? You may have more than one setuptools installed. If there is a link to lower

Basic file version diff algorithm

廉价感情. 提交于 2019-12-04 12:15:41
问题 I'm looking for a solution to compare two versions of the same file to get a representation of the changes/differences. 回答1: If it's plain text, then Google's diff-match-patch library ought to do what you want (it has a C# version). If it's binary data, then look into the things people do to apply updates to executables (bsdiff and Courgette). They look for the minimum difference between two files so that a smaller update can be sent out to end users. Sounds similar to your needs. 回答2: For

How can I upgrade the SVN version used by git svn in Windows?

℡╲_俬逩灬. 提交于 2019-12-04 10:19:48
My company is in the process of upgrading SVN to 1.7. Checking git svn --version shows that the SVN version being used is 1.4.6. I'd like to get the version of SVN that git svn uses up closer to 1.7. However, I've seen no instructions for updating the version of SVN that git svn uses (in Windows). The other thread I found looking for answers seems to be oriented to a Mac OSX user. I haven't seen Windows instructions for this upgrade, however. Does anyone know how to properly update the SVN version for git svn in Windows? I'm assuming you're using mSysGit on Windows, since I'm using a recent

PyPI 400 upload error

一世执手 提交于 2019-12-04 10:15:45
问题 I created a package in PyPI named virtdc. I made some changes and uploaded 2 different versions 0.1.0 and 0.1.1. Now I deleted version 0.1.1 through the PyPI web interface and try to upload again with the same version number. It is giving me error as follows ... Writing virtdc-0.1.2/setup.cfg Creating tar archive removing 'virtdc-0.1.2' (and everything under it) running register Registering virtdc to http://pypi.python.org/pypi Server response (200): OK running upload Submitting dist/virtdc-0

NSFoundationVersionNumber and iOS Versions

你离开我真会死。 提交于 2019-12-04 10:13:25
Well, my questions is really simple i guess. I use NSFoundationVersionNumber to check the version of my app , and make it both compatible with iOS6 and iOS7 . if (NSFoundationVersionNumber > NSFoundationVersionNumber_iOS_6_1 ){ //Here goes the code for iOS 7 } else if (NSFoundationVersionNumber == NSFoundationVersionNumber_iOS_6_1){ //Here goes the code for iOS 6.1 } Well,as far as i know, Apple has released 6.1.X versions.So, using the second "else-if" statement, versions 6.1.X are excluded from the list of compatible versions i make?If yes is the answer, then how can i determine ,if the

What is the Android Bundle Version and Version Code and how do they relate?

一笑奈何 提交于 2019-12-04 10:04:28
问题 a) What does the Android bundle version and version code denote? b) What is the difference between the bundle version and version code? i) Suppose I have a bundle version of 0.137 , how does the version code relate to this? Can the version code just be 137? ii) What happens when I release bundle version 1.0 next? Can I just call the version code 10 ? c) How do they relate? What's the right way to number the bundle versions? N.B. There does not seem to be a source that explains the difference,

node.js 中的npm模块版本管理

时间秒杀一切 提交于 2019-12-04 08:56:21
semver npm 中的模块版本都需要遵循 semver 2.0 的语义化版本规则。 版本格式:主版本号.次版本号.修订号,版本号递增规则如下: 主版本号:当你做了不兼容的API 修改, 次版本号:当你做了向下兼容的功能性新增, 修订号:当你做了向下兼容的问题修正。 先行版本号及版本编译信息可以加到“主版本号.次版本号.修订号”的后面,作为延伸。 然后基于语义化的版本,我们在选择版本的时候就可以对依赖进行版本的控制: dependencies: { "express" : "3.x" , "debug" : "*" , "express-session" : "~1.0.0" , "connect-redis" : "1.2.3" } 从例子中可以看到,有许多种选择版本范围的风格,可以在 semver in npm 上看到每一个不同风格的作用。 而在 node.js 的模块管理中,最常用到的几种是: *: 任意版本 1.1.0: 指定版本 ~1.1.0: >=1.1.0 && < 1.2.0 ^1.1.0: >=1.1.0 && < 2.0.0 其中 ~ 和 ^ 两个前缀让人比较迷惑,简单的来说: ~ 前缀表示,安装大于指定的这个版本,并且匹配到 x.y.z 中 z 最新的版本。 ^ 前缀在 ^0.y.z 时的表现和 ~0.y.z 是一样的,然而 ^1.y.z 的时候,就会

How do we determine whether we are using Web API 1 or Web API 2?

戏子无情 提交于 2019-12-04 08:46:44
问题 Introduce the problem I would like to know whether we are using Web API 1 or 2. My own packages.config indicates version 5.0.0. Is that Web API 1 or 2? Search, and research I have tried Googling the following: "web api 1" "web api 2" and ASP.NET Web API release history and ASP.NET Web API nuget The best references seem to be these two nuget pages: ASP.NET Web API Nuget seems to indicate that anything 4.* is Web API 1, Microsoft ASP.NET Web API 2.1 Nuget that anything 5.* is Web API 2. Is that

Gem dependencies versions meaning

旧城冷巷雨未停 提交于 2019-12-04 08:06:40
问题 Gem dependency version can be specified with prefixes = , < , > , <= , >= and ~> . I understand all except last one, what does ~> mean? 回答1: The ~> operator means: match within the same version, depending on how specific you want it to be, here's some examples: Specification From ... To (exclusive) ">= 3.0" 3.0 ... ∞ "~> 3.0" 3.0 ... 4.0 "~> 3.0.0" 3.0.0 ... 3.1 "~> 3.5" 3.5 ... 4.0 "~> 3.5.0" 3.5.0 ... 3.6 Source 来源: https://stackoverflow.com/questions/3492772/gem-dependencies-versions

How do I require a specific version of a ruby gem?

倾然丶 夕夏残阳落幕 提交于 2019-12-04 07:42:36
问题 Specifically, the ruby-oci8 gem. I have both 1.0.7 and 2.0.4 installed. I want 1.0.7. I can just require oci8, but I don't get the version I want. irb(main):001:0> require 'oci8' => true irb(main):002:0> OCI8::VERSION => "2.0.4" I can require using the full path to the file, which works, but is not going to be portable: irb(main):001:0> require 'C:\Ruby\lib\ruby\gems\1.8\gems\ruby-oci8-1.0.7-x86-mswin32-60\lib\oci8' => true irb(main):002:0> OCI8::VERSION => "1.0.7" I can use the gem command