In Pkg3, if your script uses a particular environment, which can be project-local (i.e. local to the repository the script is in) then as long as you don't change the version of anything in that environment, it won't change. I wasn't planning on having a way of indicating a particular version in the source code at the point of loading something, however.
On Fri, Nov 4, 2016 at 6:30 PM, Tom Breloff <t...@breloff.com> wrote: > Not that I know of. Hopefully the next generation package manager (Pkg3) > will enable this sort of conditional pinning. It should at least enable > dual environments. > > > On Friday, November 4, 2016, Tom Lee <m...@tomlee.id.au> wrote: > >> Hi all, >> >> Is there any way to specify that "using" or "import" should load a >> specific package version without pinning the package to a particular >> version globally? I would like to prevent my older scripts breaking when >> packages are updated while still using the latest version by default. >> >> Thanks, >> >> Tom >> >
