| 1 |
On 2011å¹´06æ02æ¥ 01:45, Serkan Kaba wrote: |
| 2 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 3 |
> Hash: SHA1 |
| 4 |
> |
| 5 |
> Just chatted with Jesus. He stated that wildcard imports are considered |
| 6 |
> bad practice and not needed for Python 2.5 compatibility. Is there a |
| 7 |
> specific reason why you migrated to wildcard imports (Jython |
| 8 |
> incompatibility maybe?) |
| 9 |
|
| 10 |
I didn't migrate *to* wildcard imports but migrate *from*. |
| 11 |
The original version which my branch branched from is in wildchar form |
| 12 |
(you can see the version in trunk: |
| 13 |
https://overlays.gentoo.org/svn/proj/java/projects/java-config-2/trunk/src/java_config_2/EnvironmentManager.py |
| 14 |
,it has wildchar form) |
| 15 |
The reason why I migrate to not use wildcard form is just the above, as |
| 16 |
said, the wildchar imports are discouraged and moreover, they even do |
| 17 |
not compile in Jython 2.5. (Though wildchar form do compile in Python |
| 18 |
2.6, Jython's implementation is more strict maybe) |
| 19 |
> |
| 20 |
> - -- |
| 21 |
> Sincerely, |
| 22 |
> Serkan KABA |
| 23 |
> Gentoo Developer |
| 24 |
> -----BEGIN PGP SIGNATURE----- |
| 25 |
> Version: GnuPG v2.0.17 (GNU/Linux) |
| 26 |
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
| 27 |
> |
| 28 |
> iEYEARECAAYFAk3mesUACgkQRh6X64ivZaKNmQCfVI2JpFoC5P+/yQnmTgTDVWCg |
| 29 |
> riEAn182dk/yWtcIh5UIoJwR/ePHNmVQ |
| 30 |
> =4c63 |
| 31 |
> -----END PGP SIGNATURE----- |
| 32 |
|
| 33 |
|
| 34 |
-- |
| 35 |
Best regards, |
| 36 |
Jiale Pan(Kyle Pan) |
Archives