gitimport | Import python packages directly from a git repository

by fourplusone Python Version: 1.2.0 License: MIT

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | gitimport Summary

gitimport is a Python library. gitimport has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can install using 'pip install gitimport' or download it from GitHub, PyPI.

Import python packages directly from a git repository

Support

Quality

Security

License

Reuse

Support

gitimport has a low active ecosystem.

It has 5 star(s) with 0 fork(s). There are 1 watchers for this library.

It had no major release in the last 12 months.

gitimport has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of gitimport is 1.2.0

Quality

gitimport has 0 bugs and 0 code smells.

Security

gitimport has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

gitimport code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

gitimport is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

gitimport releases are not available. You will need to build from source code and install.

Deployable package is available in PyPI.

Build file is available. You can build the component from source.

Top functions reviewed by kandi - BETA

kandi has reviewed gitimport and discovered the below as its top functions. This is intended to give you an instant insight into gitimport implemented functionality, and help decide if they suit your requirements.

Find a ModuleSpec for a given module
Return the entry for the given key
Execute a module
Return the code for this entry

Get all kandi verified functions for this library.

gitimport Key Features

No Key Features are available at this moment for gitimport.

gitimport Examples and Code Snippets

No Code Snippets are available at this moment for gitimport.

Community Discussions

Trending Discussions on gitimport

Empty keywords fields after migration from CVS to GIT using cvs2git

QUESTION

Empty keywords fields after migration from CVS to GIT using cvs2git

Asked 2020-Feb-25 at 10:28

I am migrating many repositories from CVS to GIT. I used cvs gitimport first, but it didn't work properly. cvs2git works (almost) fine. Unfortunately there is one issue that worked in cvs gitimport and does not work in cvs2git (and is important for me) After migration using cvs2git, fields containing keywords (in specific files) are empty:

$Header$

$Revision$

$Author$

$Date$

"filename" Revision: 1.2

I tried different configurations of: ctx.revision_collector, ctx.revision_reader,_keyword_handling but the effect is still the same.

The main commands I used:

cvs2git --blobfile=cvs2git-tmp/${module}-tmp/git-blob.dat --dumpfile=cvs2git-tmp/${module}-tmp/git-dump.dat --username=migrationuser --encoding=ascii --encoding=utf8 --encoding=cp1250 --encoding=iso8859_2 --fallback-encoding=ascii --retain-conflicting-attic-files ${module}

git --bare init "projectname" cd "projectname" cat ../../cvs2git-tmp/git-blob.dat ../../cvs2git-tmp/git-dump.dat | git fast-import git branch -D TAG.FIXUP git gc --prune=now git repack -a -d -f

Has anyone managed to solve such a problem? Thank you in advance for your answer

...

ANSWER

Answered 2020-Feb-24 at 22:15

I use the cvsconvert program from cvs-fast-export

It mostly expands keywords as a CVS user would expect them to be expanded (I'm not sure if it handles $CVSHeader$ or a custom LocalKeyword defined in CVSROOT/config, but I'll be testing that soon).

Once you've converted to Git, IFF you want to continue using per-file keyword expansion then you might consider using Git's $Format:$ feature which is enabled by setting the export-subst attribute for all files needing such expansions, and generating your releases with git-archive(1). Note these are only expanded when the release is created with git archive, but generally that's when they're most useful anyway.

For example I replace my old occurrences of $Id$ or $CVSHeader$ with something like the following (adapted where necessary for different comment or string constant syntax, and of course with the actual project name and file path):

Source https://stackoverflow.com/questions/60380819

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install gitimport

You can install using 'pip install gitimport' or download it from GitHub, PyPI.
You can use gitimport like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: