Earlier quoted context omitted.
Here we go :) Packaging, the easy way Because I'm not on a blog, I can't go too much into details, and I'm sorry about that. It would be better to take more time on each point, but use them as starting point. I'll assume you know what virtualenv and pip. If you don't, check a tutorial on them first, it's important. But I'm going to go beyond packaging, because it will make your life much easier. If you want to skip c…
Oh, almost forget. 6 - If you want to compile Python to an exe, use nuitka ( http://nuitka.net/ ), not p2exe, cx_freeze and co.
Current State of Python Packaging
71–77 of 77 posts
Re: Current State of Python Packaging
#72Earlier quoted context omitted.
Here we go :) Packaging, the easy way Because I'm not on a blog, I can't go too much into details, and I'm sorry about that. It would be better to take more time on each point, but use them as starting point. I'll assume you know what virtualenv and pip. If you don't, check a tutorial on them first, it's important. But I'm going to go beyond packaging, because it will make your life much easier. If you want to skip c…
Oh, almost forget. 6 - If you want to compile Python to an exe, use nuitka ( http://nuitka.net/ ), not p2exe, cx_freeze and co.
Re: Current State of Python Packaging
#73Earlier quoted context omitted.
Oh, almost forget. 6 - If you want to compile Python to an exe, use nuitka ( http://nuitka.net/ ), not p2exe, cx_freeze and co.
You need to put this all somewhere better than a HN comment. I will then immediately share it on HN (-:
I will have to open an english on I guess.
Re: Current State of Python Packaging
#74Earlier quoted context omitted.
Oh, almost forget. 6 - If you want to compile Python to an exe, use nuitka ( http://nuitka.net/ ), not p2exe, cx_freeze and co.
P.S. no src/ folder? I feel like that's quite a nice idea, although I come from a Java background, so perhaps it just feels familiar.
Nevertheless, if you want to have one, just add this to setup.cfg
[options]
package_dir=src
packages=find:Re: Current State of Python Packaging
#75Earlier quoted context omitted.
From the little development I have done in Rust, I have to agree. On the other hand, I’ve been working with react-Native and typescript recently, and it’s a constant mess. Every invocation of yarn leaves at least a couple of warning messages about things that are out of my control. Installing packages is slow and at least every few days I have to wipe out node_modules and nuke any iOS build folders in order to get it…
NPM claims to have taken the lead from Yarn in terms of install speed in the latest versions. Still, I prefer Yarn because NPM has such a history of suckage. Meanwhile, the former CTO of NPM released a new (alpha) package management system last week at JSConfEU (the conference where NodeJS was first announced); see https://github.com/entropic-dev/entropic/blob/master/docs/RE...
Re: Current State of Python Packaging
#76Re: Current State of Python Packaging
#77I get mad at the Haskell tools I use every day, and then I remember that nobody else is really in better shape.