Currently, after building a library and use twine upload dist/* to publish it to PypiCloud, a pre-release version will be created. When I install it using pip, I will have to add --pre tag. How can I publish a "not pre-release" version instead?
Related
Has anyone installed Pythonnet on Python 3.10.0 (was pre-installed with Mac OS)? When I try to install Pythonnet through PIP, it complains that there is some issue with the package, and not with PIP!! After searching a bit on Google , I found that Pythonnet is currently not supported on Python 3.10.
So the next step was to install an older version (supported) of Python e.g. 3.7 on Mac and then make it the default Python environment. However, even after using the right set of commands, I'm unable to do switch from 3.10 to 3.7.
enter image description here
Can someone please tell me where am I going wrong?
Try installing a preview with --pre pip parameter. Python.NET 3.0.0 is currently in preview and is about to be released, it supports Python 3.10.
I'm trying to understand why the easy_install of pyicu works and pip install doesn't (see below). also trying to understand "What is the difference between a PyPi project with a universal wheel and one without?" Will installs be "easier?". If so, will this merge request solve the problem of polyglot not installing on an Anaconda machine?
Need help/advice/solutions on how to best resolve python project install issue that is tied to underlying dependencies. I have two local fixes in GitHub Gists but would like to know the best way to have this fix "out there" so people like me can find it. What is the normal Python Community approach? The problem centers around three projects:
polyglot - a python multilingual NLP toolkit
pyicu - Python extension wrapping IBM's International Components for Unicode C++ library (ICU).
pycld2 - CLD (Compact Language Detection) library as maintained by Dick Sites
The goal:
Install polyglot on a MacOSX computer running Python Anaconda Distribution
Make the fix I found available to everyone; lots of issues published about the problem.
Here's the error trace:
The Problem (Lots of them):
Core polyglot dependency, pyicu, does not properly install when you use pip install. Discovered you must use easy_install for it build properly and work on MacOSX. If you don't use the easy_install, you get:
polyglot requires icu 54.1.1 to run in Anaconda, but...
Homebrew, the MacOSX tool to install icu, only installs version 58.1. That version is too new. Old stackoverflows advise brew install icu4c to fix problem, but Homebrew evolution makes that advice obsolete now.
pyicu does not have a universal wheel; but I created a merge request to add one to pyicu. Only way to fix this is with this channel's icu, https://anaconda.org/ccordoba12/icu. conda install icu will not work, but that's the normal conda way of doing things.
*pycld2 - CLD (Compact Language Detection) becomes a problem because after I build the wheel file locally, have to download the project and run setup.py install locally. There has to be a better way to do this right?
What I've Done to Solve the problem (should I do more, what should I do next?)
Created two Gists that can successfully install polyglot on a Mac running Anaconda for Python 2.7 or Python 3.5
Python 2.7 fix
Python 3.5 fix
created the merge request for pyicu
Both Gist fixes work. But, is this error in install tied to the wheel? If I installed pyicu with easy_install, the install works. But, with pip, it doesn't?
What are the steps to take in the Python community to fix it so people can find the solution or just pip install with no problems?
I did a test, and if the wheel file is built, the pip works with no issues.
I'm currently using Elm version 17.1 and want to try an application that uses version 18. I'm on Ubuntu.
Is there a way to temporarily upgrade to version 18 and then revert afterwards?
Otherwise what is the best approach?
You can use the npm package elm-version-manager to install multiple versions of Elm alongside each other (with the command evm install 0.18.0 or evm install 0.17.1) and switch which one is 'active' (with evm use 0.18.0 or evm use 0.17.1) systemwide.
you can use npm. As without global flag, npm packages can be installed for local project folder.
Im'm trying to upgrade my dotnet cli. I have installed in my Mac (OS El Capitan) from the official link.
But when I try to view the version with this code:
dotnet --version
My output:
1.0.0-preview2-003121
How can I upgrade?
The version 1.0.0-preview2-003121 of the .Net CLI is currently the latest released version. So there is no newer released version to upgrade to.
You could upgrade to the latest build from the dotnet/cli repo, but you probably shouldn't, since that's not a released version.
To update from 2.0.3 to 2.1.4 I simply downloaded the installer from Microsoft's website and then ran the installer.
`https://download.microsoft.com/download/1/1/5/115B762D-2B41-4AF3-9A63-92D9680B9409/dotnet-sdk-2.1.4-osx-gs-x64.pkg
I had a Terminal window open, and when I did a dotnet --version before and after running the installer, the correct version was output to the console. I did not have to restart my terminal window even.
Microsoft has done a good job at packaging the SDK and CLI together. See either their main dotnetcore website or go to their git
I built the KRuntime using AppVeyor. Its artifacts from artifacts\build\*.nupkg are in its nuget feed. How do I install this KRuntime build using the Version Manager?
Try downloading the package to your local machine, then:
kvm install KRE-svr50-x64.1.0.0-t140627040749.nupkg
Your milage may vary. I get this output:
C:\Users\chris\Downloads>kvm install KRE-svr50-x64.1.0.0-t140627040749.nupkg
Unpacking to C:\Users\chris\.kre\packages\temp
Installing to C:\Users\chris\.kre\packages\KRE-svr50-x64.1.0.0-t140627040749
Cannot find KRE-svr50-x86.1.0.0-t140627040749, do you need to run 'kvm install 1.0.0-t140627040749'?