barneygale / isoparser Goto Github PK

Hello,

Could you update the pip package to include the long_description fix that you committed? When I try to install it, I get the following

(ansible-2.0) SEA-ML-RUPP1:f5-ansible trupp$ pip install isoparser
Collecting isoparser
  Downloading isoparser-0.1.tar.gz
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/private/var/folders/jc/9d1188j962931rhqrlm4173w5j5m45/T/pip-build-pe1410/isoparser/setup.py", line 11, in <module>
        long_description=open('README.rst').read(),
    IOError: [Errno 2] No such file or directory: 'README.rst'
    
    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /private/var/folders/jc/9d1188j962931rhqrlm4173w5j5m45/T/pip-build-pe1410/isoparser/

Trying this fails:

$ pip install isoparser
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-build-uxXWyM/isoparser/setup.py", line 11, in <module>
        long_description=open('README.rst').read(),
    IOError: [Errno 2] No such file or directory: 'README.rst'

README.rst is not included in the package.

Or add the python version in pypi.

THANKS. :)

The ISO we are using (from VMware website) has a sub-directory named "[BOOT]". When I get the records from the ISO and list the names of each directory, your code returns "BOOT". Can you please fix this?

I can see you have all of the iso metadata in there, which is exactly what I'm after. I can't find a built-in method/mechanism for extracting it. While it's possible to iterate over an iso object using something like iso.volume_descriptors['primary'].dict.items(), I wonder if you have a more direct, supported, object method rather than digging into the private dict membership directly?

In basic usage, a set of strings can be passed as the path argument for method iso.record(). For example:

iso.record("boot", "grub").children

It works well in Python 2, but in Python 3 a KeyError will always be raised with the same code. This is due to the difference of string types between Python 2 and 3. In Python 2, default string type is same as binary type which can be looked up in path_table directly. However, things changes in Python 3.

It looks more convenient and nature to support both legacy strings and unicode strings in this method. Then, it also helps users to write Python 2-3 compatible code with the isoparser library.

I don't know ISO9660 at all what I'm about to ask maybe completely silly.

I have an ISO that contains a kickstart file. I would like to change the contents of ks.cfg just by reading in the ISO and change the content of the record then something like iso.save()

My ISO is rather large, I was hoping not to have to extract the iso then repackage it backup and with an overlay. Depending on how ISO9660 stores it's data, that write my as well be a complete rebuild of the ISO.

Thoughts?

https://github.com/matteomattei/PySquashfsImage

iso url was trying to write a iso dump script , dump squashfs

then automate the dump of squash fs to tmp then tarball it , ie can a chroot , then shove to docker...

i'm new ish to python scripting..

Read-only blu-ray iso support would be great.

After all, this is called isoparser, not iso9660parser ;-).

I know it's a big request, no pure python implication exists atm. I'm sure a lot of people would find this usefull.

Thanks!!!

Hi I see there is a mismatch between the source code of the repo (which works for me) and the package in pypi, could we get the code released?

Thanks