[Numpy-discussion] Re: 1D ndarray to java double[]
Getting back to this, byteswap() looks like a general endian solution for ndarrays: https://stackoverflow.com/questions/49578507/fast-way-to-reverse-float32-endianness-in-binary-file The examples there specify float32 format for opening a file, but that seemed to scramble the header that was output. No header being the desired behavior for the BE file, which happened to occur when using byteswap from the same program that made the mem-mapped data that was the normal ndarray, in which case no header was written (conveniently for java). Little-endian access can be handled in java with ByteBuffer.order(). Bill -- Phobrain.com On 2023-01-01 08:31, Jerome Kieffer wrote: > On Sun, 01 Jan 2023 05:31:55 -0800 > Bill Ross wrote: > > Thanks! > > Java is known to be big-endian ... your CPU is probably little-endian. > $ lscpu | grep -i endian > Byte Order: Little Endian > > Numpy has the tools to represent an array of double BE. > Is there a lower-level ndarray method that writes an array that could be > used this way? One example: [not applicable, redacted over bounce of previous try] ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: bross_phobr...@sonic.net___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
[Numpy-discussion] next NumPy Newcomers' Hour - 12 pm UTC
Our next Newcomers' Hour will be held this Thursday, March 23rd at 12 pm UTC. Stop by to ask questions, share your progress, celebrate success, or just to say hi. To add to the meeting agenda the topics you’d like to discuss, follow the link: https://hackmd.io/3f3otyyuTte3FU9y3QzsLg?both Join the meeting via Zoom: https://us06web.zoom.us/j/82563808729?pwd=ZFU3Z2dMcXBGb05YemRsaGE1OW5nQT09 -- Cheers, Inessa Inessa Pawson Contributor Experience Lead | NumPy https://numpy.org/ GitHub: inessapawson ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
[Numpy-discussion] dropping support for Gitpod and our Docker image builds
Hi all, We received a notification from Docker that there Free Team organization no longer exists, and that we have until April 14 to upgrade to a paid tier. We only use Docker to support Gitpod. Gitpod builds have been broken in main for quite a while (see https://github.com/numpy/numpy/actions/workflows/gitpod.yml). Since it's a cron job that doesn't show up on PRs, but I get the notifications. Overall, Gitpod has been useful during some sprints, but it has proven to be too much maintenance effort. Maintaining a Docker team, CI jobs for building 2 Docker images, and a nontrivial amount of code and docs is no longer a good tradeoff. Here is what we have related to Gitpod: https://github.com/numpy/numpy/tree/main/tools/gitpod https://github.com/numpy/numpy/blob/main/.github/workflows/docker.yml https://github.com/numpy/numpy/blob/main/.github/workflows/gitpod.yml https://github.com/numpy/numpy/blob/main/doc/source/dev/development_gitpod.rst https://hub.docker.com/u/numpy We have a reasonable alternative, which is GitHub Codespaces. All it currently requires is ~lines of simple to understand code ( https://github.com/numpy/numpy/tree/main/.devcontainer) and no CI jobs. We have one tracking issue for feedback in case you try it and find gaps: https://github.com/numpy/numpy/issues/23134. It doesn't pre-build NumPy locally, but that's only 1-2 minutes of wait time and is something a new contributor anyway has to learn about. The dev environment is reproducible, so this isn't much of a hurdle. We need replacement docs for that, but they can be much simpler I'd say. It's basically "go to https://github.com/codespaces/, hit the green button, and select the numpy repo, then it'll drop you into a VSCode IDE with a ready to go dev env". So my proposal is to drop all the Docker Hub and Gitpod related code and docs. I have already discussed this with Tania Allard, who did most of the heavy lifting on the initial creation of the Gitpod machinery (for SciPy, which was then synced to NumPy). Thoughts? Cheers, Ralf ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
[Numpy-discussion] Re: dropping support for Gitpod and our Docker image builds
I'm in favor of dropping Gitpod, IMO during sprints as well, it yielded less utility than expected initially, and breaks far too often (as summarized above). It would also be good to be free from docker rot given their recent changes. --- Rohit On Mar 20 2023, at 9:09 pm, Ralf Gommers wrote: > Hi all, > > We received a notification from Docker that there Free Team organization no > longer exists, and that we have until April 14 to upgrade to a paid tier. We > only use Docker to support Gitpod. Gitpod builds have been broken in main for > quite a while (see > https://github.com/numpy/numpy/actions/workflows/gitpod.yml > (https://link.getmailspring.com/link/26a16109-f730-429d-b189-c4597c5af...@getmailspring.com/0?redirect=https%3A%2F%2Fgithub.com%2Fnumpy%2Fnumpy%2Factions%2Fworkflows%2Fgitpod.yml&recipient=bnVtcHktZGlzY3Vzc2lvbkBweXRob24ub3Jn)). > Since it's a cron job that doesn't show up on PRs, but I get the > notifications. > > Overall, Gitpod has been useful during some sprints, but it has proven to be > too much maintenance effort. Maintaining a Docker team, CI jobs for building > 2 Docker images, and a nontrivial amount of code and docs is no longer a good > tradeoff. > > Here is what we have related to Gitpod: > https://github.com/numpy/numpy/tree/main/tools/gitpod > (https://link.getmailspring.com/link/26a16109-f730-429d-b189-c4597c5af...@getmailspring.com/1?redirect=https%3A%2F%2Fgithub.com%2Fnumpy%2Fnumpy%2Ftree%2Fmain%2Ftools%2Fgitpod&recipient=bnVtcHktZGlzY3Vzc2lvbkBweXRob24ub3Jn) > https://github.com/numpy/numpy/blob/main/.github/workflows/docker.yml > (https://link.getmailspring.com/link/26a16109-f730-429d-b189-c4597c5af...@getmailspring.com/2?redirect=https%3A%2F%2Fgithub.com%2Fnumpy%2Fnumpy%2Fblob%2Fmain%2F.github%2Fworkflows%2Fdocker.yml&recipient=bnVtcHktZGlzY3Vzc2lvbkBweXRob24ub3Jn) > https://github.com/numpy/numpy/blob/main/.github/workflows/gitpod.yml > (https://link.getmailspring.com/link/26a16109-f730-429d-b189-c4597c5af...@getmailspring.com/3?redirect=https%3A%2F%2Fgithub.com%2Fnumpy%2Fnumpy%2Fblob%2Fmain%2F.github%2Fworkflows%2Fgitpod.yml&recipient=bnVtcHktZGlzY3Vzc2lvbkBweXRob24ub3Jn) > https://github.com/numpy/numpy/blob/main/doc/source/dev/development_gitpod.rst > > (https://link.getmailspring.com/link/26a16109-f730-429d-b189-c4597c5af...@getmailspring.com/4?redirect=https%3A%2F%2Fgithub.com%2Fnumpy%2Fnumpy%2Fblob%2Fmain%2Fdoc%2Fsource%2Fdev%2Fdevelopment_gitpod.rst&recipient=bnVtcHktZGlzY3Vzc2lvbkBweXRob24ub3Jn) > https://hub.docker.com/u/numpy > (https://link.getmailspring.com/link/26a16109-f730-429d-b189-c4597c5af...@getmailspring.com/5?redirect=https%3A%2F%2Fhub.docker.com%2Fu%2Fnumpy&recipient=bnVtcHktZGlzY3Vzc2lvbkBweXRob24ub3Jn) > > We have a reasonable alternative, which is GitHub Codespaces. All it > currently requires is ~lines of simple to understand code > (https://github.com/numpy/numpy/tree/main/.devcontainer > (https://link.getmailspring.com/link/26a16109-f730-429d-b189-c4597c5af...@getmailspring.com/6?redirect=https%3A%2F%2Fgithub.com%2Fnumpy%2Fnumpy%2Ftree%2Fmain%2F.devcontainer&recipient=bnVtcHktZGlzY3Vzc2lvbkBweXRob24ub3Jn)) > and no CI jobs. We have one tracking issue for feedback in case you try it > and find gaps: https://github.com/numpy/numpy/issues/23134 > (https://link.getmailspring.com/link/26a16109-f730-429d-b189-c4597c5af...@getmailspring.com/7?redirect=https%3A%2F%2Fgithub.com%2Fnumpy%2Fnumpy%2Fissues%2F23134&recipient=bnVtcHktZGlzY3Vzc2lvbkBweXRob24ub3Jn). > It doesn't pre-build NumPy locally, but that's only 1-2 minutes of wait time > and is something a new contributor anyway has to learn about. The dev > environment is reproducible, so this isn't much of a hurdle. We need > replacement docs for that, but they can be much simpler I'd say. It's basically "go to https://github.com/codespaces/ (https://link.getmailspring.com/link/26a16109-f730-429d-b189-c4597c5af...@getmailspring.com/8?redirect=https%3A%2F%2Fgithub.com%2Fcodespaces%2F&recipient=bnVtcHktZGlzY3Vzc2lvbkBweXRob24ub3Jn), hit the green button, and select the numpy repo, then it'll drop you into a VSCode IDE with a ready to go dev env". > > So my proposal is to drop all the Docker Hub and Gitpod related code and > docs. I have already discussed this with Tania Allard, who did most of the > heavy lifting on the initial creation of the Gitpod machinery (for SciPy, > which was then synced to NumPy). > > Thoughts? > > Cheers, > Ralf > > ___ > NumPy-Discussion mailing list -- numpy-discussion@python.org > To unsubscribe send an email to numpy-discussion-le...@python.org > https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ > Member address: rgosw...@quansight.com ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.o
[Numpy-discussion] Re: dropping support for Gitpod and our Docker image builds
On Mon, Mar 20, 2023 at 3:13 PM Ralf Gommers wrote: > Hi all, > > We received a notification from Docker that there Free Team organization > no longer exists, and that we have until April 14 to upgrade to a paid > tier. We only use Docker to support Gitpod. Gitpod builds have been broken > in main for quite a while (see > https://github.com/numpy/numpy/actions/workflows/gitpod.yml). Since it's > a cron job that doesn't show up on PRs, but I get the notifications. > > Overall, Gitpod has been useful during some sprints, but it has proven to > be too much maintenance effort. Maintaining a Docker team, CI jobs for > building 2 Docker images, and a nontrivial amount of code and docs is no > longer a good tradeoff. > > Here is what we have related to Gitpod: > https://github.com/numpy/numpy/tree/main/tools/gitpod > https://github.com/numpy/numpy/blob/main/.github/workflows/docker.yml > https://github.com/numpy/numpy/blob/main/.github/workflows/gitpod.yml > > https://github.com/numpy/numpy/blob/main/doc/source/dev/development_gitpod.rst > https://hub.docker.com/u/numpy > > We have a reasonable alternative, which is GitHub Codespaces. All it > currently requires is ~lines of simple to understand code ( > https://github.com/numpy/numpy/tree/main/.devcontainer) and no CI jobs. > We have one tracking issue for feedback in case you try it and find gaps: > https://github.com/numpy/numpy/issues/23134. It doesn't pre-build NumPy > locally, but that's only 1-2 minutes of wait time and is something a new > contributor anyway has to learn about. The dev environment is reproducible, > so this isn't much of a hurdle. We need replacement docs for that, but they > can be much simpler I'd say. It's basically "go to > https://github.com/codespaces/, hit the green button, and select the > numpy repo, then it'll drop you into a VSCode IDE with a ready to go dev > env". > > So my proposal is to drop all the Docker Hub and Gitpod related code and > docs. I have already discussed this with Tania Allard, who did most of the > heavy lifting on the initial creation of the Gitpod machinery (for SciPy, > which was then synced to NumPy). > > Thoughts? > > Cheers, > Ralf > > That's fine with me. I did run it a couple of times to see what it did and the setup time excruciating :) If removing it also reduces the maintenance burden, so much the better. Chuck ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
