@anythonywritescode I liked this video and thought that you did a great job explaining how to do the setup file. I look forward to watching more of your content and learning how to package software correctly.
I am new to python and am trying to get up to speed on it. I understand that we could re-write a setup.cfg file easier than setup.py file, but why would we need to programmatically re-write this data in the first place? Maybe a few example cases when we would need to change this data would be helpful.
github.com/asottile/setup-cfg-fmt has a few good examples, basically if you want to format or normalize or automatically improve the setup metadata it'd be impossible with setup.py
How would you deal with automating the version in the setup.cfg when building the package if you’d have the version defined somewhere in an / __version__.py or similar.
imo don't bother, you _rarely_ need it at runtime and if you do you can retrieve it using `importlib.metadata.version('pkgname')`: th-cam.com/video/beDG6Ibo2zQ/w-d-xo.html
in that case you'd probably have two setup.py files (containing the `name` / `version`) that share the `setup.cfg`? seems a little bit of a weird setup though :thinking:
First I saw the video for 2 minutes, then I realized I also need to watch other things other than the keyboard. So I came to comment this and will continue the video again
Thx again - these "small" examples/tips are right what I need :thumbsup: ! What is the reason for using `exit(main))` instead of just `main()` in main.py?
Do you know about poetry and what do you think about such tools? And for the find packages in setup.cfg you can specify where to look, so you could do a src directory where you put your package( s) , no meed to exclude any new or other folders like docs etc.
yes, I know about poetry and the 3-4 similar tools. imo they slow down development more than helping it and poetry in particular has some very harmful opinions about versioning that make library development an absolute pain
@@anthonywritescode why dont you like static project metadata in pyproject.toml? Even using setuptools, which is already supporting PEP621. Just curious
@@anthonywritescode Okay, but am not understanding how it would work in python 3.12? Python now raises deprecation warnings for setuptools and calling setup.py installs. If I write it in setup.py won't it be an issue in future? Or is there a way to call commands in setup.py with pip install?
setuptools is not deprecated, nor is setup.py -- the communication on this is terrible from pypa and it's leading to all sorts of misunderstandings. the things that are deprecated are distutils and calling setup.py directly. pip will do the right thing though
@@anthonywritescode Got it, maybe I explained myself poorly, if calling setup.py directly is deprecated and if I have custom cmds in my setup.py how do I call it without setup.py. Right now what we do is `python setup.py mycustomcommand` how should it be called when setup.py won't be allowed to be called directly?
Can u make a video explaining pkg versions in setup, specifically __version__.py file. Ive noticed both pytest/requests using it , but couldnt figure out the right way. (have a pr on the line here...)
they're using setuptools-scm which I do not recommend -- I talk about semantic versioning here: th-cam.com/video/vRSw2f34RRU/w-d-xo.html and I just write the version directly in setup.cfg as I show in this video
This man's brain is running at a frequency that I can't even fathom. Really cool, informative video. Exactly what I'm looking for.
glad it helped!
Legendary, as basic as this is, it was something I was looking for. Top lad
This was extremely more helpful than dealing with StackOverflow jerks. Thank you for this.
@anythonywritescode I liked this video and thought that you did a great job explaining how to do the setup file. I look forward to watching more of your content and learning how to package software correctly.
I am new to python and am trying to get up to speed on it. I understand that we could re-write a setup.cfg file easier than setup.py file, but why would we need to programmatically re-write this data in the first place? Maybe a few example cases when we would need to change this data would be helpful.
github.com/asottile/setup-cfg-fmt has a few good examples, basically if you want to format or normalize or automatically improve the setup metadata it'd be impossible with setup.py
Thanks man this was very cool and informative.
Great tutorial! It helped me setup this program called babi
How would you deal with automating the version in the setup.cfg when building the package if you’d have the version defined somewhere in an / __version__.py or similar.
imo don't bother, you _rarely_ need it at runtime and if you do you can retrieve it using `importlib.metadata.version('pkgname')`: th-cam.com/video/beDG6Ibo2zQ/w-d-xo.html
what is the blue icon ad on you have in your browser. how about the one next to it?
that's probably bitwarden (password manager) and tampermonkey (user scripting engine)
If we want to declare two setup package in setup.cfg how can we do it. As it will have two "name,version,etc.
in that case you'd probably have two setup.py files (containing the `name` / `version`) that share the `setup.cfg`? seems a little bit of a weird setup though :thinking:
First I saw the video for 2 minutes, then I realized I also need to watch other things other than the keyboard. So I came to comment this and will continue the video again
at first, i though he was gonna make one project with the left hand and another with the right hand at the same time.... bummer.
hah! at one point I learned one-handed touch typing -- could get almost ~60 wpm (left hand only)
Thx again - these "small" examples/tips are right what I need :thumbsup: !
What is the reason for using `exit(main))` instead of just `main()` in main.py?
I cover that in this video: th-cam.com/video/sv46294LoP8/w-d-xo.html -- it doesn't make any difference in this particular example though
@@anthonywritescode got it :-))
Do you know about poetry and what do you think about such tools?
And for the find packages in setup.cfg you can specify where to look, so you could do a src directory where you put your package( s) , no meed to exclude any new or other folders like docs etc.
yes, I know about poetry and the 3-4 similar tools. imo they slow down development more than helping it and poetry in particular has some very harmful opinions about versioning that make library development an absolute pain
hi atually I passed -e . in requirements.txt but I am getting ERROR: File "setup.py" no found.Directory cannot be installed in editable mode.
well, did you read what the error message says?
Python "package" - giggity
how do you include stub (.pyi) files in the package with setuptools
check out these:
- th-cam.com/video/bfyIrX4_yL8/w-d-xo.html
- th-cam.com/video/n4GJ8rp6DpE/w-d-xo.html
Link to "pyproject.toml explained" is missing (:
yeah, I don't use it and don't recommend it
@@anthonywritescode why dont you like static project metadata in pyproject.toml? Even using setuptools, which is already supporting PEP621. Just curious
Gracias me ayudó mucho gracias
¡de nada!
Hi. Nice tutorial, how do we handle custom commands via cmdclass in setup.cfg?
it doesn't support it -- for any non simple things you need to write them in setup py. it's a nice forcing function though
@@anthonywritescode Okay, but am not understanding how it would work in python 3.12? Python now raises deprecation warnings for setuptools and calling setup.py installs. If I write it in setup.py won't it be an issue in future? Or is there a way to call commands in setup.py with pip install?
setuptools is not deprecated, nor is setup.py -- the communication on this is terrible from pypa and it's leading to all sorts of misunderstandings. the things that are deprecated are distutils and calling setup.py directly. pip will do the right thing though
Following is the warning I see, SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
@@anthonywritescode Got it, maybe I explained myself poorly, if calling setup.py directly is deprecated and if I have custom cmds in my setup.py how do I call it without setup.py. Right now what we do is `python setup.py mycustomcommand` how should it be called when setup.py won't be allowed to be called directly?
A short tutorial on pyscaffold package will be helpful. Could you do one please? Thanks.
I've never used it personally -- I usually just use `cp` to make my new projects
Please help me understand the following Python behavior:
def foo():
x = 1024
my_list = [1024]
def helper():
x = 2048
my_list[0] = 2048
return
helper()
print(x) # Stuck at 1024 😞
print(my_list[0]) # Changed to 2048 🙂
return
foo()
Thanks!
sure! check out this video where I explain what's going on here: th-cam.com/video/evYOlT1T7Mo/w-d-xo.html
@@anthonywritescode Thank you very much. This really helped.
Can u make a video explaining pkg versions in setup, specifically __version__.py file. Ive noticed both pytest/requests using it , but couldnt figure out the right way. (have a pr on the line here...)
they're using setuptools-scm which I do not recommend -- I talk about semantic versioning here: th-cam.com/video/vRSw2f34RRU/w-d-xo.html and I just write the version directly in setup.cfg as I show in this video
@@anthonywritescode would you recommend shifting to pyproject.toml?
I'm not using it
Good !!
life saver!
Thanks!
Wouldn't able to fix the issue without seeing the commas you added at setup.py script. - Thanks!
Who is this guy?
who me?