[HN Gopher] Python Modern Practices
       ___________________________________________________________________
        
       Python Modern Practices
        
       Author : synergy20
       Score  : 25 points
       Date   : 2024-07-02 21:56 UTC (1 hours ago)
        
 (HTM) web link (www.stuartellis.name)
 (TXT) w3m dump (www.stuartellis.name)
        
       | jw887c wrote:
       | >Avoid using Poetry for new projects. Poetry predates many
       | standards for Python tooling. This means that it uses non-
       | standard implementations of key features, such as the dependency
       | resolver and configuration formats in pyproject.toml files.
       | 
       | What? This is the first I've heard of this.
        
         | SCUSKU wrote:
         | Was going to comment the same thing. Would love to hear the
         | author expand further on why not use Poetry. I've found it to
         | be pretty solid and continue to use Poetry + Pyenv for all my
         | projects, but open to hearing the case for PDM or Hatch.
        
           | hobs wrote:
           | One thing I saw which was weird as hell was poetry has
           | serious issues with changing windows requirements
           | (specifically removing them) and has a tendency to throw all
           | sorts of fun errors (its method of removing files is not file
           | system friendly.)
           | 
           | As far as I can tell the issue is still open and has been for
           | awhile.
        
         | spacephysics wrote:
         | Yeah to me Poetry was a game changer in dependency tooling. Not
         | that better tooling can come about, but it's recently worked
         | great on multiple production grade projects.
         | 
         | No complaints, and has shoot-in-the-foot safety features
        
         | tinix wrote:
         | pyenv? great! then just use pip with requirements.txt...
         | 
         | what's wrong with pip freeze? why are there so many competing
         | tools?
         | 
         | it's very anti-python IMO.
        
         | agumonkey wrote:
         | I recall some discussion on the extended tool configuration,
         | the section names have seen different conventions over time.
        
       | helsinki wrote:
       | I've not had any issues using mamba environments and vanilla pip.
       | Not sure why I would need to change that? I have packages that
       | thousands of people use, and others that help manage billions of
       | dollars. I've managed to keep things simple without upgrading
       | tooling. This article feels like it's suggesting flavor of the
       | month technologies without explaining why the status quo is bad.
       | Also, you can't really use virtualenvs easily when you have
       | packages that depend on C libraries.
        
       | martinky24 wrote:
       | Overall, generally reasonable. Nothing is a hard and fast rule,
       | if you know what you're doing and have a good reason for going
       | down an alternative path, that's great. But if on a new project
       | you generally follow these you'll be setting yourself up for
       | success.
        
       ___________________________________________________________________
       (page generated 2024-07-02 23:00 UTC)