Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
P PyNEMO
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 37
    • Issues 37
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • thopri
  • PyNEMO
  • Merge requests
  • !69

Merged
Created 3 years ago by thopri@thopriMaintainer

update YML file to specify matplotlib and cftime versions

  • Overview 6
  • Commits 1
  • Changes 1
  • Loading...

Created by: jpolton

I had to specify matplotlib version (3.2) to avoid issues with basemap. And cftime=1.4.1 to avoid issues with utime.

This was tested on livljobs8 with module load anaconda/3-5.1.0

The utime thing is a ticket

Loading
Loading

  • thopri
    thopri @thopri · 3 years ago
    Maintainer

    Created by: thopri

    I remember having issues too, I tried to make the environment yml file as simple as possible to give conda more flexibility in solving issues like these. But its not perfect, I am wondering if we should put min of python 3.6? I know my development was done past that point and there was quite a big change from 3.5 to 3.6

  • thopri
    thopri @thopri · 3 years ago
    Maintainer

    Created by: jpolton

    I remember having issues too, I tried to make the environment yml file as simple as possible to give conda more flexibility in solving issues like these. But its not perfect, I am wondering if we should put min of python 3.6? I know my development was done past that point and there was quite a big change from 3.5 to 3.6

    I naively assumed it was forcing python3.7 but I see that that is not so. So yes. Specifying python version is probably a good idea. Hmm. I've added a note to the project board

  • thopri
    thopri @thopri · 3 years ago
    Maintainer

    Created by: thopri

    yeah the name of the yaml file to build the environment having 37 in it was not the best idea. I can't remember why it was called that. but yeah currently no python version is specified aside from being 3.

  • thopri
    thopri @thopri · 3 years ago
    Maintainer

    Created by: jdha

    It was called pynemo_37.yml as it specifies - python=3.7.6 I'm surprised it wasn't adding it to your env @jpolton

  • thopri
    thopri @thopri · 3 years ago
    Maintainer

    Created by: thopri

    It prob was but I have fiddled alot and not always reflected that in the environment if it wasn't critical

  • thopri
    thopri @thopri · 3 years ago
    Maintainer

    Created by: jpolton

    It was called pynemo_37.yml as it specifies - python=3.7.6 I'm surprised it wasn't adding it to your env @jpolton

    I need a holiday or an eye test. Probably both.

  • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
Please register or sign in to reply
0 Assignees
None
Assign to
0 Reviewers
None
Request review from
None
Milestone
None
Assign milestone
None
Time tracking
No estimate or time spent
0
Labels
None
Assign labels
  • No matching results
  • Manage project labels
Lock merge request
Unlocked
1
1 participant
user avatar
Reference: thopri/PyNEMO!69
Source branch: feature/yml_update

    0 pending comments