iplib3 VS gitignore

Instead of keeping all the code at the repository root, maybe consider a more traditional project structure. As far as examples go, I've got this for an executable, and I think this works for a more complex project.

What that means in practice, I have yet to figure out how to explain in the simplest way possible, but perhaps an example repository might help somewhat. The details more or less boil down to

First, some values simply never change. For example, my iplib3 has plenty of hard-coded constants set by the IPv4 and IPv6 specifications and there's no need to have those in some external config file because, again, unless the standard gets updated those are constant.

I haven't touched this codebase in a while (although I really should), but it serves as one of my better examples for object-oriented programming. It's reasonably large, yet meticulously linted: https://github.com/Diapolo10/iplib3

I don't have any projects using setuptools anymore so unfortunately I can't give an example for that, but if Poetry is fine then iplib3 will probably suffice. Focus on the imports and the project structure, and maybe pyproject.toml, everything else is just noise.

Well, my GitHub profile is part of my flair in this subreddit, feel free to dig around. My latest project was an attempt to port the ms JavaScript library to Python, and I think I did alright. Other things I can highlight would be my iplib3 package, a server implementation for the EguiValet messaging service, and finally I've got a fairly unfinished text colouring utility called escapyde.

And iplib3 could use some cleanup, such as redesigning the inheritance to add support for seamless conversion between all supported types. The documentation should also be written as right now there's basically nothing.

You could maybe take a look at my iplib3 project for some examples. Alternatively, the EguiValet server project should be fine too.

While I have a very recent project that would otherwise be a perfect example, it does something a bit unusual with imports so I'll instead use iplib3 as an example, even though I haven't had time to work on it lately.

The Pytest documentation does a much better job at explaining how this works in practice than I ever could. I don't have any super simple example repositories, but iplib3 might work: https://github.com/Diapolo10/iplib3/blob/main/tests/test_address.py

In conclusion, the Gitignore repository stands as a testament to the power of collective knowledge and collaboration in software development. By providing a centralized repository of .gitignore templates, it empowers developers to streamline their workflow, maintain cleaner repositories, and focus on what they do best – writing exceptional code. As the software development landscape continues to evolve, the significance of .gitignore templates as indispensable tools for developers is set to endure.

The challenge here was actually from my #48in28 Exercism participation, where I am pretty familiar the standard layout for some repositories since I am familiar with tooling and language, working with new languages does not come with the same familiarity, so I found it made sense to use canonical definitions, hence the use of github/gitignore.

Add .env to your .gitignore file to prevent it from being committed. Here's an example file with it already added. You may also use dotenv for advanced configuration and it will automatically load environment variables from a .env file into process.env.

Here you can find ready-made .gitignore templates for various technologies and languages such as Python, Java, Kotlin, Go, and many others: https://github.com/github/gitignore/tree/main.

You could also use this git ignore template. Create you .gitignore and add the contents from that file in.

I've only used free Unity with GitHub or GitLab, professionally and reaching back into internships. One recommendation would be to use a slightly longer .gitignore than the default, like this one.

Virtual Environments are a feature that has been part of python itself since version 3.3. It allows you to isolate both a python version and any packages you install with it. Every python project I develop with uses a virtual environment for such isolation purposes. Now I generally like to create these virtual environments inside the target project's directory so I know exactly what it's tied to. If you use GitHub's python gitignore file naming the virtual environment folder as venv or .venv will ensure it doesn't get committed (which you don't want). So I'll make a new project folder and create a virtual environment inside of it:

Especially considering the GitHub .gitignore template for Node only ignores .env.local, not .local.env: https://github.com/github/gitignore/blob/main/Node.gitignore...

# Get latest from https://github.com/github/gitignore/blob/main/Unity.gitignore