Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

make available as a pip module #5

Open
Abe404 opened this issue Mar 15, 2023 · 2 comments
Open

make available as a pip module #5

Abe404 opened this issue Mar 15, 2023 · 2 comments

Comments

@Abe404
Copy link
Contributor

Abe404 commented Mar 15, 2023

This would make downloading/installing and version management a bit simpler. Let me know if you would like a hand :)

@nilsvu
Copy link
Owner

nilsvu commented Mar 15, 2023

This repo is mostly some sample code that people can copy and edit, not sure how useful it would be as a pip package. If you have suggestions for a feature set of a texfig package then let me know :)

@Abe404
Copy link
Contributor Author

Abe404 commented Mar 15, 2023

In my case, installing dependencies for my project (which uses texfig) requires using pip for other modules i.e pip install -r requirements.txt, but for texfig I have a shell script cloning and unziping the texfig repo, which I then use as a module.

wget https://github.com/Abe404/texfig/archive/master.zip 
unzip master.zip
mv texfig-master/texfig.py ./
rm -r master.zip 

The idea here is that texfig isn't part of my code but a separate module maintained elsewhere and pulled in when required (like a pip module). My dependency management would be slightly easier/more elegant if texfig was just an extra line in my requirements file.

Having a pip module would not necessarily mean alterations to texfig, but could simplify dependency management for me but if most users are just copy-pasting the code then perhaps there are less reasons to make this into a module.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants