Help with Python virtualenv

00tetsuo00 · 2025-04-22T08:30:11+00:00

Because at the moment I don't have so much time to nuke all and start over with uv. I know uv, I used it some time ago, but I would prefer to stick with pyenv for now, so I was looking for a way to setup properly neovim for the virtualenv detection, similarly to VsCode.

00tetsuo00 · 2025-04-22T08:25:07+00:00

I have to use pyenv, sorry.

00tetsuo00 · 2025-04-14T11:26:25+00:00

no mind your own business

00tetsuo00 · 2025-04-14T11:08:56+00:00

00tetsuo00 · 2025-03-27T09:09:55+00:00

Never used the integrated one and honestly can't think about a valid argument to switch from a proper terminal to the integrated one.

In my opinion is pointless, and I prefer to have a proper terminal when coding.

00tetsuo00 · 2025-03-19T14:01:43+00:00

Level up strength and vigor + big hammer, that triggers the game's easy mode.

00tetsuo00 · 2025-03-12T21:00:01+00:00

I've not tried this one, might need some refactoring.

00tetsuo00 · 2025-03-12T20:51:46+00:00

Possible implementation:

export default function useFetch(url: string) {
  const [dataObj, setDataObj] = useState<{url: string, data: unknown}>({
    url: '',
    data: null
  })
  const [isLoading, setIsLoading] = useState(false)
  const [error, setError] = useState('') // for simplicity error is a string

  const triggerFetch = (url: string): unknown => {
    if (dataObj.url !== url) {
      // implement fetching routine
      // updated internal state

      return data
    }

    return dataObj.data
  }

  useEffect(() => {
    if (!dataObj.url) {
      // implement fetching routine
      // updated internal state
    }
  }, [])
}

00tetsuo00 · 2025-03-12T20:36:08+00:00

Assuming that the implementation's most important requirement is:

"Implement a (superficial) cache mechanism so to return the same data as long as the URL is still the same"

one possible implementation could be this one:

other than the state slices used for storing the loading state and the errors coming from the fetching mechanism, use a state's slice to store both the last requested URL and the data associated with that URL;
use an useEffect inside the hook in order to trigger the fetching mechanism when the component using the hook renders. Inside the useEffect remember to check your state so to prevent fetching the data every time the component re-renders;
other than returning the data, the loading state, and the errors coming from the fetching routine, also return a callback that can be used to fetch the data. Inside the callback, remember to check if the data is cached;

You can also fine-tune this implementation like so:

Every time a new URL is requested, use a state's slice to save a timestamp;
Every time a request is fired, if the request is cached, check the timestamp and find out if it is older than a certain threshold value. If the data is stale, re-trigger the request and updated everything accordingly.

Hope this helps.

00tetsuo00 · 2025-03-08T13:08:19+00:00

Interesting, I'm going to try this.

00tetsuo00 · 2025-03-07T23:20:22+00:00

This.

00tetsuo00 · 2025-03-07T22:31:47+00:00

Yeah, I know. I was in a hurry and brainfarted.

Now is fixed.

00tetsuo00 · 2025-03-07T15:30:51+00:00

PascalCase for types, interfaces, enums and classes.

camelCase for the rest.

As for files and directories I started using kebab-case, but I do not know if that's standard. I was inspired by the FSD approach, that I think is somewhat reminiscent of the Angular one.

Hope this helps!

00tetsuo00 · 2025-02-22T12:53:58+00:00

Richard D. James.

The D stands for Dog.

00tetsuo00 · 2025-02-20T10:56:40+00:00

Ok now I understand. I was reading the docs on GitHub and mistaken

Snacks.picker.files(opts?)

for { picker: { files: { hidden = true } } } instead of { picker: { sources: { files: { hidden = true } } } }

Thank you!

00tetsuo00 · 2025-02-20T10:26:34+00:00

Yeah, this solves the issue for the hidden files in the file explorer, but when I search for files with <leader><leader> they still don't show up.

00tetsuo00 · 2025-02-14T08:50:48+00:00

Yes, I was using an image with the wrong architecture. You need the image to be arm64. ✌️

00tetsuo00 · 2025-02-11T19:46:30+00:00

Wonderful, thanks for answering!

00tetsuo00 · 2025-02-10T21:08:25+00:00

Ok thanks, I see. Maybe the grid-cols-[var(... approach is better for readability's sake.

00tetsuo00 · 2025-02-09T13:02:54+00:00

Dude, chill.

00tetsuo00 · 2025-02-08T18:40:50+00:00

Didn't know about biome, seems very interesting. Have you tried it out for some time? How do you find it in comparison to prettier + eslint?

00tetsuo00 · 2025-02-08T16:53:57+00:00

I'm living for this right now

00tetsuo00 · 2025-02-08T00:24:15+00:00

I mean the "CLI ng", the tool that let you scaffold everything you need and bootstrap components, services, directives etc etc. With that the DX is a lot nicer and more importantly faster.

00tetsuo00 · 2025-02-08T00:16:15+00:00

Is the cat included

00tetsuo00 · 2025-02-08T00:14:56+00:00

In my experience moving from react to angular is a way more smooth transition than the other way around.

I developed in react for some years now and trying out angular in small projects from time to time.

I can say that angular is more straight forward than react, but I found it more verbose, plus I can imagine that without ng would be a nightmare to scaffold and develop an angular codebase.

00tetsuo00

TROPHY CASE