Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #10549 > unrolled thread
| Started by | Ole Streicher <olebole@debian.org> |
|---|---|
| First post | 2018-05-16 21:50 +0200 |
| Last post | 2018-05-17 10:40 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.maint.python
PLY problem Ole Streicher <olebole@debian.org> - 2018-05-16 21:50 +0200
Re: PLY problem Piotr Ożarowski <piotr@debian.org> - 2018-05-17 10:40 +0200
| From | Ole Streicher <olebole@debian.org> |
|---|---|
| Date | 2018-05-16 21:50 +0200 |
| Subject | PLY problem |
| Message-ID | <vQaAW-5at-19@gated-at.bofh.it> |
Hi, I have (still) problems with PLY generated files in the astropy package: they are just not generated, and I have no idea how to generate them correctly. For example, there are the files astropy/coordinates/angle_lextab.py astropy/coordinates/angle_parsetab.py which are now cleaned up in d/clean, and they are somehow cached regenerated from astropy/coordinates/angle_utilities.py The latter file contains the hint # This module includes files automatically generated from ply (these end in # _lextab.py and _parsetab.py). To generate these files, remove them from this # folder, then build astropy and run the tests in-place: # # python setup.py build_ext --inplace # pytest astropy/coordinates but this seems not to fit very well into the pybuild procedure. And, I have a few more of them (in astropy/units/format). What would be the best way to regenerate them? Best regards Ole
[toc] | [next] | [standalone]
| From | Piotr Ożarowski <piotr@debian.org> |
|---|---|
| Date | 2018-05-17 10:40 +0200 |
| Message-ID | <vQmC6-3On-9@gated-at.bofh.it> |
| In reply to | #10549 |
[Ole Streicher, 2018-05-16] > # This module includes files automatically generated from ply (these end in > # _lextab.py and _parsetab.py). To generate these files, remove them from this > # folder, then build astropy and run the tests in-place: > # > # python setup.py build_ext --inplace if it's about adding build_ext's option to build command, you can do it like this: export PYBUILD_BUILD_ARGS=build_ext --inplace see uvloop's debian/rules file¹ for an example [¹] https://sources.debian.org/src/uvloop/0.9.1+ds1-1/debian/rules/?hl=4#L4 -- GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.maint.python
csiph-web