Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-7327

Check ngmix works on Python 3

    XMLWordPrintable

Details

    • 1
    • DRP F16-4
    • Data Release Production

    Description

      Check that ngmix works on python 3.

      Attachments

        Issue Links

          Activity

            tjenness Tim Jenness added a comment -

            You put the tag on the wrong place. Tags go on master not the ticket branch. The tags allow eups to work out the correct version to report for third party builds. It does not see ticket branches unless you are building that ticket branch. I added a new tag on master.

            tjenness Tim Jenness added a comment - You put the tag on the wrong place. Tags go on master not the ticket branch. The tags allow eups to work out the correct version to report for third party builds. It does not see ticket branches unless you are building that ticket branch. I added a new tag on master.

            Thanks. I added the tag before I merged, so I thought it would be included in the merge.

            fred3m Fred Moolekamp added a comment - Thanks. I added the tag before I merged, so I thought it would be included in the merge.
            swinbank John Swinbank added a comment - - edited

            tjenness — You what now? Are you suggesting that the Developer Guide isn't just irrelevant (which was my previous opinion) but actively wrong on the subject of publishing? Are run-rebuild and run-publish actually documented anywhere?

            swinbank John Swinbank added a comment - - edited tjenness — You what now? Are you suggesting that the Developer Guide isn't just irrelevant (which was my previous opinion) but actively wrong on the subject of publishing? Are run-rebuild and run-publish actually documented anywhere?
            tjenness Tim Jenness added a comment -

            I believe the commands in the developer guide to publish a package still work. frossie uses them to make a release. As I learned only this week, run-publish is used to allow Jenkins to run the publish command for you without having to log in to the server and run-rebuild allows you to do builds on lsst-dev (by running the rebuild command) that you can then publish (using either technique).

            I don't think they are documented anywhere but I might be wrong (ok, I don't know where the documentation is). I can't find the JIRA tickets that implemented the Jenkins features but I assume they are somewhere.

            tjenness Tim Jenness added a comment - I believe the commands in the developer guide to publish a package still work. frossie uses them to make a release. As I learned only this week, run-publish is used to allow Jenkins to run the publish command for you without having to log in to the server and run-rebuild allows you to do builds on lsst-dev (by running the rebuild command) that you can then publish (using either technique). I don't think they are documented anywhere but I might be wrong (ok, I don't know where the documentation is). I can't find the JIRA tickets that implemented the Jenkins features but I assume they are somewhere.

            This is what happens if you use back channels.

            Yes we have a way of publishing via Jenkins (it's related to the automated weekly job) but we're still ironing a couple of things out before it becomes "official".

            frossie Frossie Economou added a comment - This is what happens if you use back channels. Yes we have a way of publishing via Jenkins (it's related to the automated weekly job) but we're still ironing a couple of things out before it becomes "official".

            People

              fred3m Fred Moolekamp
              tjenness Tim Jenness
              Tim Jenness
              Fred Moolekamp, Frossie Economou, John Swinbank, Perry Gee, Simon Krughoff (Inactive), Tim Jenness
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Jenkins

                  No builds found.