{"action":"created","issue":{"url":"https://api.github.com/repos/numpy/numpy/issues/5479","repository_url":"https://api.github.com/repos/numpy/numpy","labels_url":"https://api.github.com/repos/numpy/numpy/issues/5479/labels{/name}","comments_url":"https://api.github.com/repos/numpy/numpy/issues/5479/comments","events_url":"https://api.github.com/repos/numpy/numpy/issues/5479/events","html_url":"https://github.com/numpy/numpy/issues/5479","id":55160167,"number":5479,"title":"Windows wheel package (.whl) on Pypi","user":{"login":"mcarans","id":3799212,"avatar_url":"https://avatars.githubusercontent.com/u/3799212?v=3","gravatar_id":"","url":"https://api.github.com/users/mcarans","html_url":"https://github.com/mcarans","followers_url":"https://api.github.com/users/mcarans/followers","following_url":"https://api.github.com/users/mcarans/following{/other_user}","gists_url":"https://api.github.com/users/mcarans/gists{/gist_id}","starred_url":"https://api.github.com/users/mcarans/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mcarans/subscriptions","organizations_url":"https://api.github.com/users/mcarans/orgs","repos_url":"https://api.github.com/users/mcarans/repos","events_url":"https://api.github.com/users/mcarans/events{/privacy}","received_events_url":"https://api.github.com/users/mcarans/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/numpy/numpy/labels/component:%20distribution","name":"component: distribution","color":"e11d21"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":61,"created_at":"2015-01-22T14:38:18Z","updated_at":"2016-02-11T23:03:58Z","closed_at":null,"body":"Please make Windows wheel packages and put them on Pypi.\r\n\r\nCurrently it is possible to download Windows wheel packages for numpy here: http://www.lfd.uci.edu/~gohlke/pythonlibs/#numpy\r\n\r\nIt would be great if the wheels were directly available on the Pypi server https://pypi.python.org/pypi/ so that they can be installed with pip."},"comment":{"url":"https://api.github.com/repos/numpy/numpy/issues/comments/183093925","html_url":"https://github.com/numpy/numpy/issues/5479#issuecomment-183093925","issue_url":"https://api.github.com/repos/numpy/numpy/issues/5479","id":183093925,"user":{"login":"njsmith","id":609896,"avatar_url":"https://avatars.githubusercontent.com/u/609896?v=3","gravatar_id":"","url":"https://api.github.com/users/njsmith","html_url":"https://github.com/njsmith","followers_url":"https://api.github.com/users/njsmith/followers","following_url":"https://api.github.com/users/njsmith/following{/other_user}","gists_url":"https://api.github.com/users/njsmith/gists{/gist_id}","starred_url":"https://api.github.com/users/njsmith/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/njsmith/subscriptions","organizations_url":"https://api.github.com/users/njsmith/orgs","repos_url":"https://api.github.com/users/njsmith/repos","events_url":"https://api.github.com/users/njsmith/events{/privacy}","received_events_url":"https://api.github.com/users/njsmith/received_events","type":"User","site_admin":false},"created_at":"2016-02-11T23:03:58Z","updated_at":"2016-02-11T23:03:58Z","body":"@carlkl: the case that we are worried about is if numpy include ``atlas.dll``, and also scipy includes ``atlas.dll``, and at some point the user upgrades scipy (and gets a newer version of ``atlas.dll``), but then scipy ends up using the old version of ``atlas.dll`` that comes from the numpy package. This is bad, because scipy may be depending on having the newer version -- so things will randomly break depending on exactly what builds of which packages are involved, and which order the user imports them. This happens because if numpy includes a DLL named ``atlas.dll`` then that will \"claim\" the name ``atlas.dll`` in the process-wide DLL namespace, and it will block any other packages from using different DLLs with that name.\r\n\r\nTwo possible solutions are (a) if the SxS/activation-contexts stuff can be made to work, it provides a way to disable the process-wide DLL namespace, or (b) if numpy contains ``numpy-atlas.dll``, and scipy contains ``scipy-atlas.dll``, then they these can share the same process-wide namespace without colliding."}}