I'm trying to develop my first Julia package, FeatureEng.jl but I'm having trouble updating the package on the registry.
I've set up the GitHub actions TagBot and Register and tried updating the package version via the Project.toml file and via git tags, but I still only have one release on GitHub ("v1.0.1") and I get the following output from TagBot:
Tag v1.0.1 already exists
When I run my package in its own environment and check the version I get...
julia> using Pkg
julia> Pkg.activate(".")
Activating environment at `~/Desktop/code/julia/FeatureEng/Project.toml`
julia> using FeatureEng, PkgVersion
julia> PkgVersion.Version(FeatureEng)
v"1.2.7"
but when I install my package in a separate environment, from the general registry, and run the same check I get...
julia> PkgVersion.Version(FeatureEng)
v"1.0.1"
Am I missing something? What is the right way to publish a new Julia package version?
Thanks in advance!
Be sure you have the tagbot file on your repository
Upgrade the version number in your local Project.toml file
Commit and push to GitHub
In GitHub, add a comment to the commit with the text #JuliaRegistrator register
That's all. Tagbot will automatically create the same tag on GitHub.
Fore more details, you can have a look on my tutorial on modules and packages: https://syl1.gitbook.io/julia-language-a-concise-tutorial/language-core/11-developing-julia-packages
Related
I am trying to run AppEngine Standard Environment inside PyCharm.
The problem is when I include Google App Engine SDK as part of External Libraries, but it contains multiple version of old libraries that somehow has higher priority than the library I have in my env folder.
Specifically, it is loading jinja2-2.6 which doesn't work for Python 3, even though I have jinja2-2.11.3 in my env/lib.
Pycharm does have a bit of issues with its library system as many users have reported before. To Adjust the version of your libraries in PyCharm you must access the interpreter options relating your python interpreter for your current project, you can access this option by searching in the menu Settings/Preferences or by pressing Ctrl+Alt+S
In this dialog you can view the packages available and their current running versions. You can update the version by clicking on the ▲ symbol next to the version. if you have trouble upgrading to a specific version you may need then you can alway remove a package by clicking on the "-" on the right hand side after clicking on the package you wish to remove. After removing the package you can add a new one by clicking on the "+" button right on top of the "-" button. Here you can search for the package you need and before installing a package, you can check the specific version checkbox to search for the version you require in the dropdown menu next to it.
This link contains images for what i'm explaining here.
Remember that these packages are taken directly from the pip so if you have errors using the interface you can always try to manually edit the packages (also described in the link).
To upgrade a specific package using pip for python3 you can use the following command:
pip3 install --upgrade PackageName
I have attempted to install several packages listed at JuliaObserver which are not in the Julia registry but instead are to be downloaded from github. The instructions at JuliaObserver look like this but depending on the particular repository:
Pkg.clone("https://github.com/JuliaDataReaders/DataReaders.jl.git")
These attempts all fail with "UndefVarError: clone not defined".
Yes, Pkg.clone is part of the old API. The new API is documented here https://julialang.github.io/Pkg.jl/v1/api.html
In particular, you get a similar behaviour by
using Pkg
pkg"add <URL or package name>" # If you want to install the package
pkg"dev <URL or package name>" # If you want to develop the package
If the package is registered, you can provide the package name above. If not, you need to provide the full URL to the repo
I am developing a Julia package that I have added via dev <github url>. I can enter Pkg mode in the terminal via ] activate and get the prompt I want.
Suppose I want to change the version of Flux used with the package from v0.9.0 to v0.10.0. How do I go about doing that?
You can use pkg> update Flux or pkg> add Flux#0.10 in the same environment where you have added the package you are developing.
I'm trying to add migration package to CakePHP 3.3 using the command
composer require cakephp/migration:~1.0
but I'm receiving the following result:
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- The requested package cakephp/migration could not be found in any version, there may be a typo in the package name.
Potential causes:
- A typo in the package name
- The package is not available in a stable-enough version according to your minimum-stability setting
see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.
Read <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.
Installation failed, reverting ./composer.json to its original content.
Any suggestions to solve this?
As #ndm said its "migrations", also it should be allready installed by default if you created your app with composer or such. To activate it you just need to load it in the bootstrap.php as specified here Plugin::load('Migrations');
I'm currently working in a work environment where I do not have access to npm / node. The npm download location is actually blocked so I can't get any packages.
I want to build an Angular 2 site. As I can't access npm, I want to use Nuget to get the files. Although I can see the Angular 1 packages, I cannot seem to see any Angular 2 packages. Is there one for Nuget?
Also, is populating the node_module folder and compiling the Typescript the only thing that npm does for Angular? If I can just get a copy of the node_module folder (from outside work) and get TypeScript working in my solution, can I basically bypass the need for npm?
In short; No.
You can see a list of all available NuGet package versions here, with the most recent being 1.5.3.
Even performing a generic search shows most recent versions as 1.5.3.
Sometimes they'll have beta versions of packages available that you can install with a command similar to: Install-Package EntityFramework -Version 6.1.3-beta1 -Pre, but it doesn't appear as if they have created any pre-release packages.
So, as #Michal Dymel mentioned, you could get it from a CDN or some other location.