XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Python3 support?

    Scheduled Pinned Locked Moved Xen Orchestra
    12 Posts 3 Posters 1.7k Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • olivierlambertO Offline
      olivierlambert Vates 🪐 Co-Founder CEO
      last edited by

      I don't think there's any "plans" since XOA is build on top of Debian 10. However, we'll keep an eye on next Debian if it requires some changes.

      Regarding the dep "problem" with Python, I have no idea myself.

      1 Reply Last reply Reply Quote 0
      • DanpD Offline
        Danp Pro Support Team
        last edited by

        Looks like they plan to remove from Debian as well -- https://wiki.debian.org/Python/2Removal

        1 Reply Last reply Reply Quote 0
        • julien-fJ Offline
          julien-f Vates 🪐 Co-Founder XO Team
          last edited by

          We have no definitive plan for now but we'll keep an eye on this (and we are open to PRs).

          FYI, the issue appears to be related to xo-server > hashy > argon2.

          DanpD 1 Reply Last reply Reply Quote 0
          • DanpD Offline
            Danp Pro Support Team @julien-f
            last edited by

            @julien-f Wouldn't upgrading to a newer version of node-gyp resolved this?

            1 Reply Last reply Reply Quote 0
            • julien-fJ Offline
              julien-f Vates 🪐 Co-Founder XO Team
              last edited by

              XO does not depend on node-gyp directly.

              DanpD 1 Reply Last reply Reply Quote 1
              • DanpD Offline
                Danp Pro Support Team @julien-f
                last edited by

                @julien-f From what I can tell, there are two packages that have node-gyp as a dependency, argon2 and node-sass. Is there a way to force the process to use argon2@0.26.1 instead of argon2@0.25.1?

                1 Reply Last reply Reply Quote 0
                • julien-fJ Offline
                  julien-f Vates 🪐 Co-Founder XO Team
                  last edited by

                  I'm not familiar with it but you may found a solution there: https://classic.yarnpkg.com/en/docs/selective-version-resolutions/

                  DanpD 1 Reply Last reply Reply Quote 0
                  • DanpD Offline
                    Danp Pro Support Team @julien-f
                    last edited by

                    @julien-f The newer versions of argon2 successfully build with python3. Why not just bump the minimum argon2 package requirements for hashy?

                    1 Reply Last reply Reply Quote 1
                    • julien-fJ Offline
                      julien-f Vates 🪐 Co-Founder XO Team
                      last edited by

                      I'm thinking about it 🙂

                      1 Reply Last reply Reply Quote 2
                      • julien-fJ Offline
                        julien-f Vates 🪐 Co-Founder XO Team
                        last edited by

                        https://github.com/vatesfr/xen-orchestra/commit/1fa42a57538f36583296c63377582422f4a465df

                        0 julien-f committed to vatesfr/xen-orchestra
                        chore(xo-server): update hashy to 0.9.0
                        
                        BREAKING: requires Node >=10.
                        
                        See https://xcp-ng.org/forum/topic/3107/python3-support
                        DanpD 1 Reply Last reply Reply Quote 0
                        • DanpD Offline
                          Danp Pro Support Team @julien-f
                          last edited by

                          @julien-f 😸 👍

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post